Chit Chats MCP Server

chitchats_buy_postage

Purchase postage for a shipment using its ID. This async operation requires checking shipment status afterward to confirm completion.

Instructions

Purchase postage for a shipment. This is an async operation - check shipment status after.

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": {
      "id": "<id>"
    },
    "name": "chitchats_buy_postage"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Shipment ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose a key trait: this is an async operation, and advises checking shipment status afterward. However, it omits other important details such as side effects (financial transaction), failure modes, or whether the shipment must be in a particular state. The disclosure is partial.

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?

The description is two short sentences, front-loaded with the core action and followed by a critical behavioral note. Every sentence serves a purpose, and there is no redundant or filler content.

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 simple one-parameter tool with no output schema and no annotations, the description covers the essential action and the important async follow-up. It lacks explicit prerequisites or success/failure details, but given the tool's simplicity, the description is sufficiently complete for basic usage.

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?

The schema already describes the only parameter 'id' as 'Shipment ID' with 100% coverage. The description adds no extra parameter semantics beyond the schema, so the baseline score of 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?

The description states a specific action: 'Purchase postage for a shipment.' This clearly identifies the verb (purchase) and resource (postage for a shipment), and distinguishes it from siblings like get_rates or create_shipment. The async note adds a unique behavioral trait that further disambiguates it.

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?

The description implies usage: you have a shipment and need to purchase postage. It provides a follow-up instruction ('check shipment status after') but does not explicitly mention when to use this tool versus alternatives, nor does it give exclusions or prerequisites. Guidance is minimal but not misleading.

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