Skip to main content
Glama

research_market

Analyze market demand and buyer keywords for a product, category, or brand using structured subjects and parameters, with preview-first approval before execution.

Instructions

Preview by default. Set confirm to request approval for this exact body.

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": {
      "body": "<body>"
    },
    "name": "research_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
confirmNo
run_labelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose one genuinely important trait: the call is a preview/dry-run unless confirm is set, at which point approval is requested. That is real behavioral value. However, it never says what confirm actually executes, whether the operation is destructive, whether it costs credits, or whether approval is synchronous — all critical for a zero-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler and the default-preview behavior front-loaded, which is good structure. But the brevity is under-specification rather than concision, and 'this exact body' has no clear referent since the body schema is never described.

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

Completeness1/5

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

This is a tool with a nested object schema, a six-value enum inside subject, a 68-item parameters array, zero description coverage, no annotations, and no output schema. Against that complexity, two sentences about confirmation leave nearly everything an agent needs — purpose, cost, side effects, body structure — unexplained.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, and the nested body object has deeply structured fields (subject, parameters array, locale, market) with no documentation anywhere. The description only partially explains confirm ('approval for this exact body') and says nothing about body or run_label, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what the tool does. It says only 'Preview by default. Set confirm to request approval for this exact body,' which conveys execution semantics but nothing about researching a market, what a 'body' represents, or what result comes back. An agent reading only this text cannot tell whether the tool reads data, generates a report, or spends money.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no differentiation from siblings such as estimate_cost, list_parameters, or generate_content. The only routing signal is implicit: the default preview mode versus setting confirm, which tells the agent about a two-step flow but not which scenarios warrant this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.