Skip to main content
Glama

One Index market

get_market
Read-onlyIdempotent

Public counts for exactly one market, separately from memory and with web search. Not market shares.

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": {
      "slug": "<slug>"
    },
    "name": "get_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only 'Public counts' (hinting at no auth needed) and an unexplained 'separately from memory and with web search' fragment that raises more questions than it answers — no mention of return shape, freshness, or coverage.

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?

It is short and front-loads the resource, which is good, but brevity here comes at the cost of clarity: the second sentence is a cryptic fragment rather than information the agent can act on.

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

Completeness2/5

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

For a simple single-parameter lookup this should be easy to fully specify, yet key facts are missing: what 'counts' measures, what the slug refers to, and how people search and memory factor in. With no output schema, the description carries the full burden and does not meet it.

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% for the single required 'slug' parameter; the schema only supplies a regex pattern and length bounds with no explanation of what identifies. The description never mentions slug or clarifies that it is a hyphenated market identifier, so it does not compensate for the coverage gap.

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

Purpose3/5

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

The description conveys that the tool returns counts for a single market, and 'Not market shares' rules out one misreading of 'market'. But there is no explicit verb, and phrases like 'separately from memory and with web search' are opaque rather than distinguishing; an agent cannot confidently separate this from list_markets or get_brand.

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 or when-not-to-use guidance relative to siblings such as list_markets (which presumably enumerates markets) or get_brand. The only steer is the terse exclusion 'Not market shares', which addresses content, not tool selection.

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