Skip to main content
Glama

Stratum Market Research

Ask Stratum

ask
Read-onlyIdempotent

Ask a question about a market, figure, country, edition or price, in plain English. The answer is built only from Stratum's published pages and lists the pages to cite. Optionally pass a report slug to focus on one market.

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": {
      "question": "<question>"
    },
    "name": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportNoOptional report slug to focus on
questionYesThe question

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral value by stating the answer is grounded only in Stratum's published pages and that it returns the pages to cite, but says nothing about empty results, answer confidence, or latency.

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?

Three short sentences, front-loaded with the core action, followed by grounding behavior and the optional scoping parameter. No filler and nothing buried.

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 tool with full schema coverage and no output schema, this is close to sufficient: an agent knows what to ask, what the answer derives from, and that citations come back. Only the response shape and failure behavior are undescribed.

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 coverage is 100%, so both parameters are already documented. The description adds only a small gloss, that a report slug scopes the answer to one market, and clarifies the question is natural language; that is marginal beyond the schema baseline.

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 clear verb-plus-resource statement: ask a question about a market, figure, country, edition or price, answered from Stratum's published pages. It implicitly separates itself from the structured siblings (get_report, search_rankings) by being natural-language Q&A, but never names or contrasts with them explicitly.

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 usage guidance is about narrowing scope: optionally pass a report slug to focus on one market. There is no statement of when to prefer this over the structured lookup siblings, or when a plain search would be better, leaving selection to inference.

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