Skip to main content
Glama

Quote a platform fee

quote
Read-onlyIdempotent

The hard platform fee for a capability before it is called, with what is left of the daily cap. Never: Estimate the value of a job. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "capability": "<capability>"
    },
    "name": "quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
capabilityYesThe capability to price, as in discover, e.g. "job.create" or "invoice.issue".
mandate_tokenNoThe mandate token from mandate.create.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / capability / description
      Added value: +"The capability to price, as in discover, e.g. \"job.create\" or \"invoice.issue\"."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context beyond that: what the response contains (hard fee plus remaining daily cap) and that the call itself is 'Free.' That extra disclosure of output contents and cost-free nature is valuable.

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?

The description is extremely compact and front-loads the core purpose. The fragment 'Free.' is slightly cryptic in isolation, but nothing is wasted.

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 two-parameter, read-only, idempotent tool with no output schema, the description covers what is returned and the safety profile. It could be more explicit about whether the mandate token is optional and how the daily cap interacts, but it is largely complete.

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%, and the schema explains both parameters including the capability format and mandate token pattern. The description adds no parameter-level detail, so baseline 3 applies.

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 specific resource: the hard platform fee for a capability before invocation, plus remaining daily cap. It is clear what the tool returns, though it doesn't explicitly name a sibling alternative (e.g., compare or discover) to sharpen differentiation.

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?

'Before it is called' establishes the timing (quote prior to invoking a capability), and 'Never: Estimate the value of a job' gives an explicit exclusion. No alternatives are named, but the when/when-not conditions are clear.

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