Skip to main content
Glama

Search the PinnRadar docs

search_pinnradar_docs
Read-onlyIdempotent

Full-text search over the PinnRadar developer documentation: endpoints and their parameters, rate limits, plans, the WebSocket and SSE streams, sport ids and the JSON shape of each market. Use it for questions about how the API works, not for odds themselves. Free: it does not use any of the key's requests.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many matching sections to return
queryYesWhat to look for, in plain words

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world scope, so the safety profile is covered. The description adds genuinely non-redundant behavior: searching is free and consumes none of the key's requests, which is a quota trait the annotations cannot express. It does not describe the shape of returned sections, which is the main remaining gap.

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

Conciseness5/5

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

The purpose and the indexed scope are front-loaded in a single sentence, followed by one sentence of routing and one of cost. The long enumeration of indexed content earns its length by defining retrieval boundaries, and there is no filler wording.

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?

For a two-parameter read-only search with full schema coverage and annotations, the definition covers what is searched, when to use it, what it is not for, and its quota cost. Since no output schema exists, a brief note on what a returned section looks like would close the last 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 description coverage is 100%, with both query ("in plain words", 2-200 chars) and limit (1-5, default 3) fully documented in the schema. The description adds nothing about parameter behavior beyond the schema, so the baseline of 3 applies; the implied natural-language query style is already stated in the schema.

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?

"Full-text search over the PinnRadar developer documentation" gives a specific verb plus resource, and the enumeration that follows (endpoints and parameters, rate limits, plans, WebSocket/SSE streams, sport ids, market JSON shapes) precisely bounds what is indexed. That scoping also separates it from the odds-oriented siblings such as match_prices and price_moves.

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 questions about how the API works, not for odds themselves" supplies both an inclusion and an exclusion criterion, which is clear guidance most definitions lack. It stops short of naming the specific tool to use for odds, so the agent must infer the alternative from the sibling list rather than being routed explicitly.

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