Skip to main content
Glama

Letters Price Calculator

letters_price_calculator

Calculates the price of a configured letter for a specified organisation using the provided JSON:API payload, so you can check costs before dispatch.

Instructions

Calculate price for a letter configuration. POST /organisations/{organisationId}/deliveries/letters/price-calculator

payload is the full JSON:API document (LetterPriceCalculatorPOST) and is sent unchanged as the request body.

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": {
      "organisation_id": "<organisation_id>",
      "payload": "<payload>"
    },
    "name": "letters_price_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful behavioral facts: the exact endpoint path and that the payload is a complete JSON:API document transmitted unchanged as the request body. However, for a POST-based tool it never states that the operation is side-effect free (a compute-only quote), whether it requires authentication or organisation scoping, or how pricing errors are surfaced.

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 purpose before the endpoint and payload notes. The endpoint URL is arguably redundant with the tool name but serves as a useful pointer to the underlying contract.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This tool takes a nested, fully undocumented payload object and has no output schema, yet the description explains neither the shape of LetterPriceCalculatorPOST nor what the calculated price result looks like. For a pricing endpoint over a complex nested document, that leaves the agent without enough to construct a valid call or interpret a response.

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 0%, so the description must compensate, and it partially does by defining 'payload' as a full JSON:API document of type LetterPriceCalculatorPOST sent unmodified. It adds nothing about organisation_id and does not enumerate any of the payload's required fields, leaving the nested object shape entirely undocumented.

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 verb and resource ('Calculate price for a letter configuration') and pins it to the price-calculator endpoint, which distinguishes it cleanly from the sibling write tools like letters_create and letters_send. It stops short of explicitly stating what it is not, but the intent is unambiguous.

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 guidance on when to call this rather than letters_create or letters_send, nor any statement of prerequisites such as whether a letter must already exist or whether this is a pre-send quote step. The agent must infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.