Skip to main content
Glama

Ask Bestie Cars

Car registration ranking

get_ranking
Read-onlyIdempotent

Models ranked by rounded share of new registrations within the category and month in Sweden; change is percentage points versus the previous available consecutive month.

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": {
      "category": "<category>"
    },
    "name": "get_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
osNoNot applicable to cars; omit.
brandNoOnly this brand
limitNoMax products (default 10)
monthNoMonth as YYYY-MM. Defaults to the latest month.
regionNoSweden / SE / se only. Omit for Sweden. Other markets are unavailable.
categoryYes"new cars", "electric cars", "EVs", or category id cars/electric/suv/sedan/hatchback/estate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"\"new cars\", \"electric cars\", \"EVs\", or category id cars/electric."New value: +"\"new cars\", \"electric cars\", \"EVs\", or category id cars/electric/suv/sedan/hatchback/estate."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description does add real value by defining how the numbers are computed — rounded share and percentage-point change versus the previous available consecutive month — which matters because there is no output schema. It says nothing about ordering, tie-breaking, or what the 'previous available consecutive month' fallback means when a month is missing.

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?

A single dense sentence with the core metric front-loaded and the change definition appended after the semicolon. Nothing is wasted, though the compression makes the ranking versus change distinction slightly harder to parse on first read.

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?

For a read-only, single-required-parameter tool with full schema coverage and no output schema, the description covers what the returned ranking represents and how the change figure is derived. The remaining gap is that the shape and ordering of the returned list are never described.

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 coverage is 100%, so every parameter including category synonyms, the month format, limit bounds, and the Sweden-only region constraint is already documented in the schema. The description reinforces the category/month semantics but adds no new parameter-level meaning, so the baseline applies.

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 states a specific resource and metric: models ranked by rounded share of new registrations, scoped to a category and month in Sweden, with change measured against the previous consecutive month. An agent can tell this is a ranking/leaderboard tool rather than a lookup like get_product or compare_products, though no sibling is named explicitly.

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 and no reference to alternatives such as best_in_category or trending, which an agent would plausibly confuse with this. The only routing signal is implicit market scoping ('in Sweden'), which the schema already enforces.

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