Skip to main content
Glama

Where a brand sits against rivals

get_brand_position
Read-onlyIdempotent

One brand's position at an airport this morning: its price index and rank on price, share of days it has the cheapest offer, customer rating and rank, each rating sub-score against the airport average, depot type, the rivals priced closest to it, and the brands that are rated higher while priced lower. Useful for positioning, a competitor review or a brand health check.

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": {
      "airport": "<airport>",
      "brand": "<brand>"
    },
    "name": "get_brand_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesBrand name, partial match is fine, e.g. Hertz, Sixt, Europcar.
airportYesIATA airport code, e.g. AKL, SYD, LHR, MAD. See list_airports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the freshness model ('at this morning') and by enumerating exactly what data comes back in the absence of an output schema. It does not specify cost, rate limits, or how many rivals are returned.

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?

Front-loaded with the core statement of what is returned, followed by a compact use-case sentence; there is no filler. The output enumeration makes the first sentence dense and comma-heavy, but every listed item maps to a real data field that the missing output schema would otherwise have to convey.

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 no output schema and only two fully documented parameters, the description carries the burden of explaining the return value, and it does so thoroughly item by item. Minor gaps remain: units/scaling of the price index, whether comparisons are airport-local, and how many closest rivals are included.

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%: both parameters carry their own descriptions with examples and a pointer to list_airports. The description contributes nothing beyond restating that one brand and one airport are involved, so the baseline 3 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?

States a specific resource with scope: 'One brand's position at an airport this morning', then enumerates the concrete figures returned (price index, rank, cheapest-share, rating sub-scores, depot type, closest rivals). The output list implicitly separates it from rate-oriented siblings like get_brand_rates and get_market_rates, but it never names an alternative, so the differentiation is inferred rather than stated.

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?

Offers use-case framing ('useful for positioning, a competitor review or a brand health check'), which is genuine when-to-use context. However, it gives no when-not conditions and no routing against siblings such as get_ratings or get_market_snapshot, which overlap on rating and market content, so the agent must guess which tool is the better fit.

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