HotCodePush

Search the docs

search_docs

Read-only

Search the HotCodePush documentation by keyword, with the search of the docs site itself. Use this first for any question about setting up or using HotCodePush: the SDKs for React Native, Expo, Capacitor and Cordova, the CLI, channels, releases, rollouts, rollbacks or the API. The answer is documented, and a guessed SDK method or CLI flag breaks the app. Needs no token. Returns the matching pages, best first, each with its title and url and its best matching headings and paragraphs, each with the url of its anchor. Do not use this to read a page: call get_doc_page with a url from the results. Do not use it for the account's own organizations, apps, channels or releases: those are the account tools, such as list_apps.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_docs"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	The pages to return at most, e.g. 3. Defaults to 5, maximum 20.
`query`	Yes	The search terms, e.g. "rollback" or "capacitor install". Plain keywords work best; no search operators are supported.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/openWorld/non-destructive, and the description adds genuinely new context: no token required, results are ranked best-first, and each hit carries `title`, `url`, plus matching headings and paragraphs with anchor URLs. That return-shape disclosure matters since there is no output schema. It stops short of exhaustive behavior (no rate limits, no note on empty-result behavior), so 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then priority, then return shape, then exclusions — a sensible ordering. It runs five sentences and the topic enumeration plus the anti-guessing rationale ("a guessed SDK method or CLI flag breaks the app") is slightly expansive, but each sentence carries routing or behavioral information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only search with no output schema, the description supplies everything needed: scope, ranking, returned fields, auth requirement, and the follow-up tool for reading a page. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%: `query` documents plain-keyword behavior and no-operator support, and `limit` documents default 5 and max 20. The description repeats the keyword framing but adds no syntax, format, or semantic detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Search the HotCodePush documentation by keyword") and scopes it to the docs site's own search. It explicitly names what it is not for and which siblings cover those cases (`get_doc_page`, `list_apps`), so an agent can route correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit priority rule ("Use this first for any question about setting up or using HotCodePush"), enumerates the covered topics (SDKs, CLI, channels, releases, rollbacks, API), and states two negative cases with the alternative to use instead. When-to-use, when-not-to-use and alternatives are all present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HotCodePush tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.