Skip to main content
Glama

Ballistic

Ballistic pricing

get_pricing
Read-onlyIdempotent

Ballistic’s fee: the rate, when it is charged, what is free, and which costs belong to the chain or the launchpad. Returns the pricing page in full. Read-only.

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the trailing 'Read-only' only repeats structured data. What the description does add is content scope: the page is returned in full, and it lists the categories of information included. It says nothing about response shape or size, which matters given there is no output schema.

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 short sentences, front-loaded with the substance (what the fee page covers) before the return-mode statement. The only waste is the closing 'Read-only', which duplicates readOnlyHint and earns no space.

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-parameter, read-only lookup with no output schema and no nested objects, an agent mainly needs to know what content comes back — and the description supplies that at the category level. It is nearly complete; only the distinction from estimate_fee is left unstated.

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 schema imposes no semantic burden and the baseline of 4 applies. The description's enumeration of returned cost categories is a reasonable substitute for parameter detail, though it describes output rather than input.

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 a specific resource (Ballistic's fee schedule) and enumerates its contents: the rate, when it is charged, what is free, and whether costs belong to the chain or the launchpad. That is far more than a restatement of the name. It stops short of naming a sibling such as estimate_fee, so an agent must infer the boundary itself.

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?

Usage is only implied: 'Returns the pricing page in full' suggests this is the reference/documentation lookup rather than a computed quote, which hints at the difference from estimate_fee. There is no explicit when-to-use or when-not-to-use statement, and the sibling that overlaps most (estimate_fee) is never mentioned.

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