Skip to main content
Glama

fulfil_store_order

Destructive

Mark a paid store order as fulfilled after it has been dispatched. Optionally record its tracking link.

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": "fulfil_store_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
trackingUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the mutation profile is covered. The description adds the precondition state gate, which is genuinely useful, but says nothing about reversibility, whether the order's status can be un-fulfilled, or how repeat calls behave given the non-idempotent hint.

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 zero filler; the core action leads and the optional parameter is mentioned second. Nothing could be removed without losing information.

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

Completeness3/5

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

For a destructive, non-idempotent mutation on a single order, the definition covers the action and precondition but leaves out the consequences (what state transition occurs, whether it can be undone, whether dispatch evidence is required). With no output schema, return values need not be described, which limits the gap somewhat.

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 description coverage is 0%, so the description must carry parameter meaning; it does explain the optional tracking link, which maps to trackingUrl. However, the required id parameter is never mentioned (format, which order identifier is expected), and it doesn't note that trackingUrl defaults to an empty string.

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 gives a specific verb and resource ("Mark a paid store order as fulfilled") plus two state preconditions (paid, dispatched). The verb 'fulfil' is plainly distinct from the read-only siblings get_store_order and list_store_orders, though no sibling is named explicitly.

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?

It clearly states the conditions under which the tool applies: the order must be paid and already dispatched. It gives no explicit when-not guidance or alternatives (e.g. what to do if the order is unpaid or undelivered), which keeps it short of a 5.

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