Skip to main content
Glama

Model prices and specs

get_model_prices
Read-onlyIdempotent

What a model really costs in Bulgaria: used and new price range and median from open listings and real sales in the last 180 days, plus official specs, gaming score and the cheapest open listings. Accepts a slug or a name.

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": {
      "model": "<model>"
    },
    "name": "get_model_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
modelYesSlug or name, e.g. 'rtx-3060' or 'GeForce RTX 3060'

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 establish that this is a safe, closed-world, idempotent read, so the description need not repeat that. It does add behavioral context the annotations cannot: the data is derived from open listings plus real sales, is windowed to the last 180 days, and is scoped to the Bulgarian market — all of which affect how much an agent should trust the numbers. Auth requirements and failure behavior are left unstated.

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 sentence, front-loaded with the value proposition ('What a model really costs in Bulgaria') followed by the returned data items and the input hint. Dense but every clause carries information; only the trading of 'plus official specs, gaming score' into the same sentence makes it slightly breathless.

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, the description correctly takes on the burden of describing return values, and it does so item by item. What is missing is the currency/unit of the price figures, the role of the optional 'kind' parameter, and what happens when a model slug is not found.

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 only 50%: 'model' is documented with a slug-or-name example, but 'kind' has an enum and no explanation. The description reinforces the slug-or-name flexibility of 'model' but says nothing about 'kind' — whether it narrows results, is optional, or changes the response shape. At partial coverage this is adequate but not compensating.

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

Purpose5/5

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

The description names a specific resource (model prices/specs) and enumerates exactly what comes back: new and used price range and median, official specs, gaming score, and cheapest open listings. That detail distinguishes it from find_models (discovery) and get_listing (single listing) without needing to open a schema.

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 guidance and no named alternative, even though the catalogue contains find_models and get_listing that plausibly overlap. The geographic qualifier ('in Bulgaria') hints at scope but never states the condition under which this tool, rather than a search or listing tool, should be chosen.

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