Skip to main content
Glama

facts_search

PRO ($0.01). Wikipedia search for background facts: up to 10 matching articles with snippets, and summaries for the top 3.

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

Input Schema

NameRequiredDescriptionDefault
maxNo
queryYes
access_tokenNoSubscriber token from /success (or Authorization: Bearer)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description adds useful behavior context: it is a paid PRO tool costing $0.01, searches Wikipedia, and returns up to 10 articles with snippets plus summaries for the top 3. However, it does not explicitly state authentication requirements, rate limits, error behavior, or whether results are paginated.

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 description is a single tightly written sentence that front-loads cost and purpose, then states the result shape. Every phrase carries useful information with no filler.

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 search tool with no output schema and no annotations, the description covers the source, result count, snippets, and top-3 summaries. It is still thin on parameter semantics and authentication behavior, especially given only 33% schema description coverage.

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

Parameters2/5

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

Schema description coverage is only 33%, so the description must compensate for undocumented parameters. The description does not explain the required 'query' parameter or the 'max' parameter, aside from loosely implying a cap of 10 articles. The access_token parameter is documented in the schema, but the other two are not.

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 states a specific verb and resource: Wikipedia search for background facts. It also clarifies the return shape: up to 10 matching articles with snippets and summaries for the top 3. It distinguishes this from news-oriented siblings by emphasizing Wikipedia background facts, though it does not explicitly name a sibling alternative.

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 'Wikipedia search for background facts' and the PRO cost note, but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent can infer this is for background factual research rather than current news, but the definition does not route among siblings.

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.