Skip to main content
Glama

Cancel mail or refresh tracking

spur_control_mail_order
Destructive

Cancel an eligible order with its provider or request fresh tracking for one mailpiece. Cancellation availability is decided by Spur and the provider; never claim a delivered piece can be recalled.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructive, open-world, non-idempotent behavior, so the description's value is in the added context: availability of cancellation is decided externally and may fail, and the agent must never assert a delivered piece can be recalled. That honesty guardrail is genuinely useful beyond the annotation set, though failure modes and post-cancel state remain unstated.

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?

Two tight sentences with the capability stated first and the honesty constraint second; no wasted wording and nothing buried.

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 destructive, no-output-schema tool, the description covers the action set, the external eligibility decision, and the truthfulness constraint. Missing only what a caller gets back or how partial failures surface, which is minor here.

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%, so the oneOf branches, action consts, identifier fields and the confirm approval flag are all fully documented in the schema itself. The description only implicitly maps 'order' and 'mailpiece' to the two branches, adding no new meaning to any parameter.

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 two specific actions — cancel an eligible order, or refresh tracking for one mailpiece — with distinct resources (order vs. mailpiece), which lets an agent tell it apart from the read-only spur_get_mail_tracking sibling. It stops short of explicitly naming that sibling as the read alternative.

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?

It implies the two use cases clearly (cancel vs. fresh tracking), but offers no explicit routing guidance such as 'use spur_get_mail_tracking to read status first' or when not to cancel. The eligibility caveat ('decided by Spur and the provider') hints at preconditions without stating them as checks the agent should make.

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