Skip to main content
Glama

Stratum Market Research

Search market reports

search_reports
Read-onlyIdempotent

Find Stratum Market Research global market reports by product, industry or keyword (for example "lithium battery", "frozen shrimp", "cardiac stents"). Returns report titles, page URLs, the headline figure with its unit and the update date. Use get_report for the full figures.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesProduct, industry or keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and a closed corpus (openWorldHint=false), so the safety profile is covered. The description goes beyond that by enumerating the return payload — titles, page URLs, headline figure with unit, update date — which tells the agent why summaries alone may be enough. It omits the result cap behavior (limit maximum 25) but that is captured in the schema.

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 sentences, front-loaded with purpose and search axes, then return contents, then the sibling handoff. No filler or redundancy; each sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, no output schema, and full annotation coverage, the description supplies everything needed: what is searched, what comes back, and where to go for deeper data. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 50%: query is documented in the schema, limit only via default/maximum/minimum. The description compensates by clarifying what query accepts (product, industry or keyword) and grounding it with three sample queries across different report categories. Limit is not explained in prose, which keeps this below a 5.

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?

States a specific verb and resource ("Find Stratum Market Research global market reports") plus the three search axes: product, industry, keyword. The concrete example queries ("lithium battery", "frozen shrimp", "cardiac stents") make the scope unmistakable, and naming get_report for depth separates it from the sibling that returns full figures.

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?

Explicitly routes the agent to get_report when the summary fields are insufficient ("Use get_report for the full figures"), giving clear context for choosing between the two. It stops short of stating when not to use this tool for other sibling paths such as search_rankings, so the routing is only partially closed.

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