Skip to main content
Glama

Listing plans and prices

get_plans
Read-only

What it costs to list an AI tool, and the ways to pay (card on Stripe, or USDC with x402).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description adds useful context beyond that by naming the two payment mechanisms (Stripe card and USDC via x402), which affects how the agent should summarize results. It says nothing about shape, currency, or whether the data is static, so it adds only modest behavioral value over the annotations.

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?

A single twenty-word sentence with no filler, and the core fact (listing cost) is front-loaded before the payment detail. Nothing could be cut without losing information.

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-param, read-only, no-input tool this is close to sufficient: it identifies the returned subject matter and the payment dimension. The one gap is that with no output schema, the description does not hint at the returned structure (plan tiers, prices, currencies), which would help the agent decide how to present results.

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 there is no parameter meaning for the description to carry; the baseline of 4 applies. The description neither misleads about inputs nor wastes space explaining nonexistent arguments.

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 states the resource concretely: pricing for listing an AI tool plus the accepted payment rails (Stripe card, USDC/x402). That resolves the ambiguity of the bare name 'get_plans', which could otherwise read as subscription or roadmap plans. It lacks an explicit verb ('returns'/'lists'), but the topic is unmistakable and no sibling (get_tool, check_listing, submit_listing, list_categories, list_deals, list_upcoming, search_tools) covers pricing.

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

Usage Guidelines3/5

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

Use is only implied by the subject matter – an agent would infer it should call this when a user asks what listing costs or how to pay. There is no explicit when-to-use sentence and no stated exclusions or alternatives (e.g., versus check_listing). Given a zero-parameter read-only tool the risk is low, but the guidance is inference rather than instruction.

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