Skip to main content
Glama

List prices

get_prices
Read-only

Use this when the user asks what something costs or what a call is charged, such as finding an email address or a phone number or running a search, or to estimate a job before running it. Returns the price of every billable item in US dollars and the version of the price list. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint true, non-destructive, closed-world), so the bar is lower, and the description still adds real signal: full enumeration of billable items, currency is USD, the response carries a price-list version, and calling it costs nothing. The 'Free' note is a behavioural fact an agent cannot infer from structured fields. It stops short of describing item identification keys, but the added context is above the annotation baseline.

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-loads the trigger, then the return payload, then the cost note in three short sentences. The example list ('finding an email address or a phone number or running a search') is slightly padded but does useful work illustrating what a billable item is.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, annotation-covered, output-schema-less tool, the description closes every gap an agent needs: when to call it, what comes back, in what currency, and that it is free. Nothing required to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline of 4 applies and there is nothing for the description to disambiguate. It correctly implies a no-argument, return-everything call.

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 verb and resource: it returns the price of every billable item, in US dollars, plus the price list version. That is concrete and lets an agent know this is a catalog-style lookup rather than a spend/usage readout. It does not explicitly distinguish itself from neighbours like get_balance or get_usage, which is the only thing keeping it off a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear positive triggers: when the user asks what something costs, what a call is charged, or to estimate a job before running it. The pre-execution estimation case is a genuinely useful routing cue. It names no exclusion or alternative tool, so the when-not side is inferred.

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