fix(integrations): correct Nimble page tool list and naming

[thierrypdamiba]

Follow-up to #1097 — the "improved version" from the Slack thread, since #1097 was intentionally merged as-is to unblock shipping the URL.

Verified against the live server, not just published docs: tools/list handshake against mcp.nimbleway.com/mcp (Nimble 3.4.3, protocol 2025-06-18) using our trial account.

The tool list was wrong: 27 tools, not 6

Nimble's docs describe six capability families, and the page reproduced those as six rows. The live server exposes 27 tools — each family ships multiple tools for synchronous, asynchronous, and status/listing calls.

This matters in Arcade specifically. The gateway tool picker lists individual tools, so someone who reads "6 capabilities" and then sees 27 checkboxes has no way to map between them. The table now carries a per-capability tool count and the total:

Capability	Tools
Search	1
Extract	2
Crawl	4
Map	1
Extract templates	7
Web search agents	11
Task results	1

Also added web search agents as a capability, which the original page omitted entirely — it's the largest family on the server at 11 tools.

Async polling gotcha

Many Nimble tools return a task ID and require polling a companion tool (nimble_task_results, nimble_agents_run_status, nimble_crawl_status). Since selecting a subset of tools is the normal gateway workflow, it's easy to build a gateway with only the starting tools and leave your agent kicking off jobs it can't read back. Now called out.

Tool naming was misleading

The page said tools appear as <your-server-id>.<tool>. Nimble prefixes its tools with nimble_, so with server ID nimble the real name is nimble.nimble_search — a doubled prefix that surprises people mid-integration. Confirmed nimble_search exists on the live server.

Cost section: attributed, not asserted

I initially removed this believing it was unsourced. That was my error — I'd only checked docs.nimbleway.com. It's published on nimbleway.com/mcp and in Nimble's MCP blog post:

"Compound accuracy over time through a Proprietary Index and Memory that gets smarter with every query"
"Cut token costs by retrieving exactly what's needed — no redundant searches, no parsing raw pages with an LLM"

Restored with two adjustments:

1. Attributed to Nimble rather than asserted as fact — product claims about a third party's internals that we can't verify from outside, on a partner-facing page.
2. Dropped the detail that outran the source. The original said the cache stores "sources, search history, and responses" and the memory layer "extracts key learnings after each run and feeds them into the next search plan." Nimble publishes "Proprietary Index and Memory" and "auditable Search Plans" — not that breakdown.

Kept the practical MCP token caveat alongside it. The two sources genuinely conflict: the product page sells retrieval efficiency, while Nimble's docs warn MCP "can consume tokens quickly" and point high-volume users at their CLI skill. Readers should see both.

Stale tool names on Nimble's marketing page

Worth passing back to Nimble: nimbleway.com/mcp advertises nimble_deep_web_search, nimble_google_maps_search, and nimble_google_maps_reviews. None of these exist on the live server. Their docs were right and their product page is out of date — a heads-up they'd probably want, since it's the page prospects read.

Style

Changelog said "Partner MCP Server"; STYLEGUIDE.md specifies lowercase "MCP server". Page body was already correct.

Verified, not changed

• Authorization: Bearer ${secret:NIMBLE_API_KEY} matches both Nimble's "store the raw key, Bearer prefix goes in the header" instruction and the ${secret:NAME} syntax in add-remote-servers — confirmed working against the live server
• All external links and internal anchors resolve, including #configure-advanced-settings
• pnpm build passes, route compiles, Vale clean (two remaining warnings are pre-existing false positives on UI labels after colons)
• Nimble absent from search/_meta.tsx, but so is Tavily — partner pages are reached via the catalog card, existing pattern
• llms.txt gives Nimble the placeholder "Documentation page", but that hits 21 entries including Tavily (generator fallback when summarization fails). Systemic, worth its own fix.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only changes to the Nimble integration page and changelog; no runtime, auth, or API behavior changes.

Overview
Updates the Nimble partner integration doc and a one-line changelog style fix so they match the live MCP server and Arcade gateway behavior.

The capabilities section now reflects seven families (including web search agents), explains that the tool picker shows ~two dozen individual tools—not one row per capability—and documents nimble_ prefixes and names like nimble.nimble_search. A callout warns gateway builders to include async polling tools (nimble_task_results, nimble_agents_run_status) with starters, and the page notes which tools write to the Nimble account.

Cost and token usage replaces the old caching narrative with Nimble-attributed retrieval claims, practical MCP token guidance (narrow tool selection, prefer search/extract), and a pointer to Nimble’s CLI skill for high-volume use.

Changelog entry wording changes Partner MCP Server to Partner MCP server for style consistency.

^{Reviewed by Cursor Bugbot for commit b1d6e47. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Jul 29, 2026 11:38pm