Skip to main content
Glama

Up to 25 components at once

research_components
Read-onlyIdempotent

A search page's worth of components in one call, charged in one transaction, at the single-call prices: without text 1 per component; with text 3 per component the first time this account reads it and 0 after. Priced before anything is fetched and refused whole if the balance cannot cover it, so check tokens_remaining first when asking for many full texts. Unknown ids come back in missing and cost nothing.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
missingNoIds that are unknown or not served (never charged)
componentsYesIn the order asked; each carries its own tokens_charged
tokens_chargedYesThe whole batch: without text 1 per component; with text 3 per newly paid full text, 0 for texts already paid
tokens_remainingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent annotations: whole-batch pricing computed before any fetch, atomic refusal with 402 when balance is short, unknown ids returned in `missing` at zero cost, and per-account caching that makes repeat text reads free. These are exactly the non-obvious behaviors an agent needs in order to avoid expensive mistakes.

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 dense sentences with no filler, and the headline batching claim leads. It is information-rich rather than padded, though the cost arithmetic is packed tightly enough that a reader must parse it twice.

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?

An output schema exists and the description correctly needn't restate returns, but it does flag the one non-obvious return case (`missing`). Cost, refusal, and caching behavior are covered; the only real gap is routing guidance versus the single-component sibling.

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?

The pricing tiering (1 vs 3 vs 0 tokens) restates what the include_text schema description already says, adding little beyond it. The description says nothing about the `guarded` flag, which is the most consequential usage decision, and nothing about the ids format beyond "components"; those live only in the nested 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?

"A search page's worth of components in one call" plus the title "Up to 25 components at once" makes clear this is a batch component-retrieval tool, implicitly distinct from the singular research_component sibling. It never states the verb outright (fetch/retrieve) or names the sibling, so the differentiation is inference rather than explicit.

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?

The only guidance is a prerequisite — "check tokens_remaining first when asking for many full texts" — plus an implicit batching hint. There is no statement of when to prefer this over research_component for a single id, or when to skip batching. Usage context is implied by cost framing rather than spelled out.

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