Skip to main content
Glama

Ask Bestie Cars

Most registered car

best_in_category
Read-onlyIdempotent

Leading new car or electric car by registration share in Sweden for a month. Includes sources. Not a quality verdict. SEK retail and separate private/business leasing observations are included where verified; USD budget filtering is unavailable.

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

Input Schema

NameRequiredDescriptionDefault
osNoNot applicable to cars; omit.
brandNoOptional brand, e.g. Volvo or Kia
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.
budget_usdNoAlso return the most picked product at or under this US price

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

A3.7/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is lower, and the description still adds real context: figures come with sources, SEK retail and separate private/business leasing observations only appear 'where verified,' and no quality judgement is implied. It does not describe the returned shape (brand, share value, month metadata), which is the remaining gap.

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?

Three compact sentences, front-loaded with the core purpose before the caveats. Each clause carries information (scope, sources, non-quality caveat, currency/leasing limits), though the final semicolon-chained sentence is dense.

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?

With 6 parameters fully documented in schema and a complete annotation set, the definition covers scope, data caveats, and geographic restriction. The one shortfall is that no output schema exists and the description only gestures at the response ('Includes sources'), leaving the exact returned fields implicit.

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 the baseline is 3. The description does add one valuable clarification beyond the schema: budget_usd is offered by the schema as functional ('most picked product at or under this US price') but the description says USD budget filtering is unavailable, flagging a trap parameter. It says nothing extra about category, month, or region beyond what the schema already documents.

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?

States a concrete resource and measure: the leading new/electric car by registration share in Sweden for a given month. The line 'Not a quality verdict' usefully separates it from a ranking/quality tool, though it never names a sibling like get_ranking or compare_products to complete the differentiation.

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 rather than stated: it is the tool for 'who leads registrations this month,' and 'Not a quality verdict' plus 'USD budget filtering is unavailable' act as exclusions. There is no explicit when-to-use/when-not framing or pointer to an alternative for market-share comparisons or multi-brand rankings.

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