fix(integrations): correct tool list against live Nimble MCP server

Verified against mcp.nimbleway.com/mcp (Nimble 3.4.3, protocol
2025-06-18) via a tools/list handshake rather than published docs.

The server exposes 27 tools, not 6. Nimble's docs describe six
capability families; each ships multiple tools for sync, async, and
status/listing calls. This matters in Arcade specifically, because the
gateway tool picker lists individual tools — someone reading "6
capabilities" then seeing 27 checkboxes has no way to map between them.
Table now carries a per-capability tool count and the total.

Added a callout on the async pattern. Many tools return a task ID and
require polling a companion tool (nimble_task_results,
nimble_agents_run_status). A gateway built with only the starting tools
selected will kick off jobs the agent cannot read back. Worth calling
out since selecting a subset of tools is the normal gateway workflow.

Resolved the open question from the previous commit: the live server has
no Google Maps tools and no nimble_deep_web_search, so the tool names on
nimbleway.com/mcp are stale. Docs were right, marketing page was not.
nimble_search confirmed present, so nimble.nimble_search stands.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: thierrypdamiba

app/en/resources/integrations/search/nimble/page.mdx

@@ -32,19 +32,28 @@ Set these under **Advanced settings → Custom headers** when you add the server
 
 ## What you can do
 
-Once you register Nimble in your Arcade project, Arcade discovers its tools automatically. They cover these capabilities:
-
-| Capability | What it does |
-| --- | --- |
-| Search | Real-time web search across multiple engines, with configurable depth and focus. |
-| Extract | Pull structured content from a specific URL, with sync and async extraction. |
-| Crawl | Crawl multiple pages with path filtering, subdomain control, and progress tracking. |
-| Map | Discover the URLs on a site through link-following and sitemaps. |
-| Extract templates | Browse, run, and generate pre-built extraction templates for popular websites. |
-| Web search agent | Create, run, and poll research agents, and read their cited results. |
+Once you register Nimble in your Arcade project, Arcade discovers its tools automatically. Nimble exposes 27 tools, because most capabilities ship more than one tool: a synchronous call, an asynchronous variant, and status or listing calls. They group into these capabilities:
+
+| Capability | Tools | What it does |
+| --- | --- | --- |
+| Search | 1 | Real-time web search with configurable content richness. |
+| Extract | 2 | Pull structured content from a specific URL, synchronously or asynchronously. |
+| Crawl | 4 | Crawl multiple pages on a site, then check progress, list jobs, or cancel a run. |
+| Map | 1 | Discover the URLs on a site by crawling its pages and sitemap. |
+| Extract templates | 7 | Browse the template catalog, run templates against a URL, and generate or refine custom ones. |
+| Web search agents | 11 | Create, update, and run research agents, then poll runs and read their results. |
+| Task results | 1 | Fetch the status and results of any async task. |
 
 Nimble prefixes its own tools with `nimble_`, and Arcade namespaces each tool under the server ID you choose when you add the server. With the server ID `nimble`, tool names appear as `nimble.nimble_search` in the Playground, the gateway tool picker, and SDK calls. Copy the exact name from the tool picker before calling it.
 
+<Callout type="info">
+  Many Nimble tools are asynchronous: they return a task ID immediately, and
+  your agent polls a companion tool such as `nimble_task_results` or
+  `nimble_agents_run_status` for the outcome. When you build a gateway, select
+  the polling tools alongside the tools that start the work, or your agent will
+  kick off jobs it cannot read back.
+</Callout>
+
 Compose these tools with Google Docs, Slack, Salesforce, GitHub, or any of Arcade's native servers in a single MCP Gateway, so an agent can research, draft, and act in one flow, with authorization and audit from Arcade's runtime.
 
 ## Cost and token usage