Skip to main content
Glama

Ballistic

Search Ballistic docs

search_docs
Read-onlyIdempotent

Keyword search over Ballistic’s public pages, glossary and documentation. Returns matching sections with their URLs. Use it for how-to questions (set up, fund, launch, sell, withdraw). A result that describes a feature that is not available today is marked, and a documentation result on a tool that differs by chain carries the site’s answer; the mark and the answer override the page. Read-only.

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

NameRequiredDescriptionDefault
limitNoHow many results. Default 5.
queryYesWhat to look for, in plain words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it describes the response shape (sections plus URLs), and warns that results for unavailable features are marked and that chain-specific doc results carry an authoritative site answer that overrides the page content.

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

Conciseness3/5

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

The opening and usage sentences are tight and front-loaded. The middle sentence about marks and answers is syntactically tangled ('a documentation result on a tool that differs by chain carries the site's answer') and forces a re-read, which undercuts otherwise efficient structure.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing returns, and it does: matching sections with URLs. For a two-parameter read-only search tool, that plus the override caveat is nearly everything an agent needs, though a clearer statement of ranking or result semantics would close the gap.

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 coverage is 100% and both parameters are documented in-schema with defaults, bounds and intent, so the baseline is 3. The phrase 'keyword search' slightly nuances the free-text query, but the description adds no format, syntax or pagination detail beyond the schema.

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

Purpose4/5

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

The description gives a specific verb and resource: 'Keyword search over Ballistic's public pages, glossary and documentation', and states the return shape ('matching sections with their URLs'). It implicitly separates itself from the sibling data tools by targeting how-to questions, but never names an alternative explicitly.

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

Usage Guidelines4/5

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

'Use it for how-to questions (set up, fund, launch, sell, withdraw)' gives concrete usage context, which is more than most definitions offer. It stops short of stating when NOT to use it or pointing to siblings like get_features or get_pricing for factual lookups.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources