Skip to main content
Glama

Stratum Market Research

Get a market report

get_report
Read-onlyIdempotent

Get the published figures of one market report as Markdown: world market size and trade value with years, growth since 2019, the largest exporting and importing countries, what the market covers, FAQs, editions and how to cite. Accepts a report slug, page URL or market name.

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": {
      "report": "<report>"
    },
    "name": "get_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportYesReport slug (e.g. "aerosol-packaging-market"), page URL or market name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing the response medium (Markdown) and enumerating what the payload contains, which matters especially because there is no output schema.

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?

Two sentences, front-loaded with verb, resource and format; the content list is dense but earns its place given the absent output schema. Slightly list-heavy, but no filler or redundancy.

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?

With one fully documented parameter and no output schema, the description correctly compensates by sketching the returned data. What remains thin is any statement of failure modes (unknown slug) or whether figures are cached/paginated, but for a simple read tool this is close to complete.

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 description coverage is 100% and the single parameter already documents slug, page URL and market name. The description restates the same three accepted forms without adding format rules, normalization behavior, or error cases, so it does not go beyond the schema.

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 ("Get the published figures of one market report") and pins down the output format ("as Markdown"). The enumeration of contents makes it unmistakably the single-report fetch operation, distinguishable from siblings like search_reports or get_ranking.

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 the scope (one report, identified by slug/URL/name), but the description never says when to prefer it over siblings such as search_reports or get_editions, nor any prerequisite or exclusion. An agent must infer the routing itself.

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