Skip to main content
Glama

BRAINIAC API catalog

Search endpoints

search_endpoints

Search paid endpoints by id, title, description, or path. Optional api is a product slug or title.

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_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it discloses little. It does not say whether matching is substring, prefix, or fuzzy, whether results are ranked or capped, whether all four fields are searched simultaneously, or what happens with zero hits. The only real disclosure is the scope word 'paid' endpoints.

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?

Two tight sentences with zero filler, and the core search semantics are front-loaded. The second sentence is slightly compressed to the point of ambiguity — 'Optional api is a product slug or title' reads as a fragment rather than a clear statement of what the parameter does.

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

Completeness3/5

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

For a simple two-parameter search tool with no output schema and no annotations, the description covers both inputs and the searchable fields, which is the minimum viable. It omits match semantics, result limits, and any sense of what comes back, leaving meaningful gaps an agent would notice at call time.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must explain both parameters, and it largely does: it names the fields the required 'query' matches and clarifies that 'api' accepts either a product slug or title. It stops short of stating that 'api' narrows the search scope or how it interacts with 'query'.

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?

States a specific verb (search) and resource (paid endpoints), and enumerates the fields matched against the query (id, title, description, path). The word 'search' distinguishes it from siblings like list_apis and describe_endpoint, though the description never explicitly contrasts with them.

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

Usage Guidelines3/5

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

Usage is implied by the field list — an agent can infer this is the lookup tool when it has a partial name, id, or path rather than an exact endpoint. There is no explicit when-to-use/when-not guidance and no named alternative (e.g., use list_apis to browse everything), so the agent must infer routing.

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