Skip to main content
Glama

Ask Bestie Cars

Registration share changes

trending
Read-onlyIdempotent

Largest changes in registration share versus the previous consecutive month. No invented trend when history is unavailable.

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": "trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPer list (default 5)
monthNoMonth as YYYY-MM. Defaults to the latest month.
sectionNocars

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description contributes one genuinely useful behavioral fact beyond that: no fabricated trend is produced when history is unavailable. It says nothing about ordering of results, tie handling, or what a thin-history response looks like, which keeps it at a 3.

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?

Two short sentences with the core purpose front-loaded and the edge-case caveat second; nothing is redundant or padded. The size matches the small amount of information the tool needs to convey.

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

Completeness3/5

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

With three optional parameters and no output schema, the description carries the burden of explaining what comes back, and it only sketches this ("largest changes"). It covers the important no-history edge case but omits result ordering, magnitude/units, and how many entries are returned by default beyond the schema's "default 5".

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%, so limit, month format, and section are already documented in the schema, establishing a baseline of 3. The description adds only marginal meaning by clarifying that "month" anchors a comparison against the prior consecutive month; it gives no further semantics for limit or section.

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?

"Largest changes in registration share versus the previous consecutive month" gives a specific metric (month-over-month share delta) and an implicit ranking behavior, which is more than a restatement of the title. It does not, however, contrast itself with siblings such as get_ranking or compare_products, so an agent must infer the distinction.

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 explicit when-to-use statement and no named alternative. The only guidance is the implied scope "versus the previous consecutive month," which tells the agent the comparison window but not when to pick this tool over the other ranking/comparison tools.

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