Skip to main content
Glama

The Meaning of Numbers

ask_site

Read-onlyIdempotent

NLWeb-style list search over published pages on this origin. Returns matching URLs and markdown twins. No paid reading.

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": "ask_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNatural-language or keyword query

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world scope, so safety is covered. The description adds the return shape (URLs plus markdown twins) and a cost hint, but leaves ranking behavior, result counts, and pagination undisclosed.

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?

Three short sentences with the purpose front-loaded and no filler. "No paid reading" is terse and slightly cryptic, but it earns its place as a cost signal.

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?

With an output schema and rich annotations, most structured detail is already carried elsewhere, and the description covers purpose, result type, and cost. It remains incomplete on when to choose this over the sibling retrieval tools, which is the main decision an agent faces.

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?

Single required parameter with 100% schema description coverage, so the baseline is 3. The description does not elaborate on query format beyond the schema's "Natural-language or keyword query", and its "NLWeb-style" framing never gets defined.

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 concrete verb and scope: "list search over published pages on this origin", and says what comes back ("matching URLs and markdown twins"). The qualifier "NLWeb-style" is unexplained jargon, but the rest of the sentence makes the resource and result type clear enough to separate it from a single-page fetch.

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

Usage Guidelines2/5

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

No when-to-use guidance and no routing to siblings such as get_page_markdown or get_site_guide. An agent must infer that this is a discovery/list step rather than a content-retrieval step; "No paid reading" only vaguely signals that results are free to access.

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