Skip to main content
Glama

Stratum Market Research

Editions and prices

get_editions
Read-onlyIdempotent

Prices in USD, delivery times and contents of the three report editions, and how to order a report or request a free sample.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_editions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that prices are in USD, which is genuine but modest extra context. It does not say the answer is static/configuration-defined, whether it reflects live or cached pricing, or that ordering itself is out of scope (no transaction is performed here).

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?

One sentence, front-loaded with the most sought-after item (prices in USD), with no filler. It does, however, bundle three distinct content areas (edition facts, pricing, purchase/sample process) into a single clause chain without structure, which is slightly harder to scan than a short list.

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?

For a zero-parameter, read-only info tool with no output schema, the description's job is to say what comes back, and it enumerates exactly that: prices, delivery times, contents, ordering steps, and free-sample path. Nothing an agent needs in order to decide to call it and interpret the answer 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?

The tool takes zero parameters and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies since the description correctly implies a no-argument catalog lookup rather than a filtered query.

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 names the resource precisely: prices in USD, delivery times, and contents of the three report editions, plus ordering and free-sample instructions. That is a clear, specific information-retrieval purpose. It stops short of differentiating itself from siblings such as get_report or search_reports, leaving the agent to infer that this is the catalog/pricing lookup rather than a report fetch.

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 content list: an agent should call this when a user asks about edition options, pricing, or how to buy or sample a report. There is no explicit statement of when not to use it, no named alternative (e.g., use get_report once an edition is chosen), and no note that this takes no arguments because it returns a fixed catalog.

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