Skip to main content
Glama

list_pricing_plans

Read-only

List JobsPipe plans and what they cost. Use it for price, credit or plan-fit questions; it returns no jobs. Returns, per plan, USD price and period, credits, price per 1,000 credits, features and signup URL, plus extra-credit and Enterprise terms.

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": "list_pricing_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoOne plan by name, e.g. builder. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / plan / description
      Previous value: -"Optional plan name to return just one plan (e.g. \"free\", \"credits\")."New value: +"One plan by name, e.g. builder. Omit for all."
  2. Changed1 schema field changed
    • changedInput schema / properties / plan / description
      Previous value: -"Optional plan name to return just one plan (e.g. \"free\", \"builder\", \"scale\")."New value: +"Optional plan name to return just one plan (e.g. \"free\", \"credits\")."
  3. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true), but the description goes further by enumerating exactly what comes back per plan: USD price and period, credits, price per 1,000 credits, features, signup URL, and extra-credit/Enterprise terms. That is meaningful disclosure for a tool with no output schema, though it omits aliases or error/empty behavior when a named plan doesn't exist.

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?

Two tight sentences, front-loaded with purpose, then use-case, then return contents. The parenthetical "it returns no jobs" sits awkwardly in the middle but earns its place as a sibling discriminator.

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 one-optional-param read tool with no output schema, the description covers purpose, when to use it, and what it returns. Nothing an agent needs in order to call it correctly is missing.

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 100% with a single parameter whose description already says "One plan by name, e.g. builder. Omit for all." The prose adds nothing about the plan argument, so the schema carries the full parameter burden; a baseline 3 is appropriate.

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?

"List JobsPipe plans and what they cost" is a specific verb plus resource, and "it returns no jobs" explicitly separates it from the job-oriented siblings. An agent can pick this for pricing questions without opening the schema.

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?

"Use it for price, credit or plan-fit questions" names concrete query types that select this tool, and the no-jobs note implicitly excludes job lookups. There is no explicit pointer to an alternative tool for adjacent questions, so the exclusion is only implied.

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