fix(integrations): stop asserting an exact Nimble tool count

The live server returned 27 tools for our account, but that number does
not belong in the docs as a fact. tools/list is auth-gated: requests
without a valid key get 401, so I could not compare what a different
plan or account sees. Our access is a partner-provided trial, which is
exactly the kind of account likely to differ from a customer's.

Arcade's own add-remote-servers guide documents this as expected
behavior: Arcade pre-loads the tools available to the user who
configures the server, and a tool unavailable to an end-user will not
appear via the gateway. So the number is per-account by design.

Now gives the reader the magnitude that matters (expect roughly two
dozen tools, not seven), says the set depends on plan and account, and
points at the guide's admin-user guidance. Capability families stay,
since those are stable across Nimble's docs and the live server.

Also added the read/write split. Most tools are read-only; the agent
create/update/run/delete and template-generation tools write to your
Nimble account, and the server marks agent deletion destructive. Worth
knowing before you drop the whole toolset into a research gateway.

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

Author: thierrypdamiba

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

@@ -32,17 +32,19 @@ 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. 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. |
+Once you register Nimble in your Arcade project, Arcade discovers its tools automatically. Nimble groups them into these capabilities:
+
+| Capability | What it does |
+| --- | --- |
+| Search | Real-time web search with configurable content richness. |
+| Extract | Pull structured content from a specific URL, synchronously or asynchronously. |
+| Crawl | Crawl multiple pages on a site, then check progress, list jobs, or cancel a run. |
+| Map | Discover the URLs on a site by crawling its pages and sitemap. |
+| Extract templates | Browse the template catalog, run templates against a URL, and generate or refine custom ones. |
+| Web search agents | Create, update, and run research agents, then poll runs and read their results. |
+| Task results | Fetch the status and results of any async task. |
+
+Most capabilities ship more than one tool: a synchronous call, an asynchronous variant, and status or listing calls. Expect roughly two dozen individual tools in the tool picker rather than seven. The exact set depends on your Nimble plan and on the account you connect with, so [connect as an admin user](/guides/mcp-gateways/add-remote-servers#save-and-confirm-the-connection) to discover the broadest list, and check the picker for what your project actually has.
 
 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.
 
@@ -54,6 +56,8 @@ Nimble prefixes its own tools with `nimble_`, and Arcade namespaces each tool un
   kick off jobs it cannot read back.
 </Callout>
 
+Most Nimble tools only read. The exceptions write to your Nimble account: the tools that create, update, run, or delete agents, and the ones that generate extract templates. If you are building a research gateway, leave the write tools out of it.
+
 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