Skip to main content
Glama

Get pricing

get_pricing
Read-onlyIdempotent

Published plans, prices, limits and availability. No authentication required.

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_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two things beyond that: the returned content categories and the fact that no authentication is needed, which meaningfully affects whether and how freely an agent can call it. It stops short of describing result shape (single vs. multiple plans, currency) but carries more than annotations alone.

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?

Two short clauses, return contents first, constraint second. Every element earns its place and nothing is padded.

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?

For a zero-argument read tool with full annotation coverage, the description plus annotations are nearly sufficient: it says what comes back and that no auth is needed. Minor gaps remain on result granularity (list of plans? single price?) and whether only publicly published tiers are included, which matters given the 'get_offers' sibling.

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, which is the baseline-4 case: there is nothing the description needs to disambiguate. The absence of arguments is consistent with a public, unfiltered catalog listing.

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 names the exact resource contents (published plans, prices, limits, availability), which tells an agent this is a public catalog-listing read. It does not, however, distinguish itself from adjacent siblings such as get_offers, get_plan_purchase, or get_usage, so the boundary between them is left to inference.

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 mention of alternatives. 'No authentication required' is a prerequisite note, not routing guidance, so an agent still has to guess whether pricing questions should be answered by this tool, get_offers, or get_plan_purchase.

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