Skip to main content
Glama
Sign In

LLM Pricing

by io.github.skakumanu
OverviewDiscussionsAdmin

get_all_pricing

Get current pricing for all LLM models from all providers

Input Schema

NameRequiredDescriptionDefault
countryNoOptional ISO-3166 alpha-2 country whose currency to use (e.g. DE -> EUR, IN -> INR). A country whose currency is unsupported yields USD with fallback_to_usd=true.
currencyNoOptional ISO-4217 code to convert prices into, alongside the canonical USD figures. Beats country. Unsupported codes return success=false listing the supported set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Optional ISO-3166 alpha-2 country whose currency to use (e.g. DE -> EUR, IN -> INR). A country whose currency is unsupported yields USD with fallback_to_usd=true.",
+  "maxLength": 2,
+  "minLength": 2,
+  "type": "string"
+}
    • addedInput schema / properties / currency
      Added value: +{
+  "description": "Optional ISO-4217 code to convert prices into, alongside the canonical USD figures. Beats country. Unsupported codes return success=false listing the supported set.",
+  "enum": [
+    "USD",
+    "EUR",
+    "GBP",
+    "INR",
+    "JPY",
+    "CAD",
+    "AUD",
+    "BRL",
+    "CNY",
+    "SGD",
+    "CHF",
+    "KRW",
+    "MXN"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but it only says pricing is 'current'. It does not disclose freshness guarantees, caching behavior, authentication requirements, rate limits, or what the returned data looks like. It is not misleading, but it is thin for a tool with no structured behavioral hints.

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?

The description is a single front-loaded sentence with no wasted words. It is appropriately sized for a simple read operation.

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?

For a low-complexity pricing lookup, the description is adequate but incomplete. It does not explain the return shape or clarify sibling boundaries, and because there is no output schema and no annotations, those gaps are more visible.

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%, and the schema fully documents the optional country and currency parameters, including enum values and fallback behavior. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 gives a clear verb and resource ('Get current pricing') and scopes it to 'all LLM models from all providers'. That scope implicitly distinguishes it from narrower siblings like get_ide_pricing or get_pricing_history, but it does not explicitly name any alternative tool.

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?

The description gives no explicit guidance on when to use this tool versus the many pricing-related siblings such as check_price_drift, get_pricing_history, compare_costs, or get_ide_pricing. Usage is only implied by the broad scope of the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LLM Pricing toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources