Skip to main content
Glama

postedly_recover_orders

Read-onlyIdempotent

Returns a Postedly browser recovery link for missing guest orders. Does not reveal orders or change ownership. Recovery requires customer email verification in the browser; subsequent order lookups remain restricted to the authorized account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "postedly_recover_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, idempotent, and closed-world status, yet the description still adds real value: the return is a capability link rather than data, it does not transfer ownership, and recovery depends on customer email verification performed in the browser. It stops short of describing link lifetime, single-use behavior, or error cases, keeping it below the top mark.

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?

Three tight sentences: the first states the action and scope, the second rules out two misreadings, the third explains the authorization flow. No filler, and the most decision-relevant fact comes first.

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 zero-parameter tool with rich annotations and no output schema, the description covers what is returned at a conceptual level, the safety posture, and the verification prerequisite. Only the practical shape of the returned link (validity window, how it is consumed) is left unexplained, which is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so per the baseline this dimension starts at 4. The description correctly implies no inputs are supplied and instead frames the required email verification as a browser-side step outside the call.

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?

States a specific verb and object ('Returns a Postedly browser recovery link') scoped to 'missing guest orders', which is far more precise than the title alone. The clause 'Does not reveal orders or change ownership' implicitly separates it from order-retrieval siblings such as postedly_orders or postedly_order_status, though no sibling is named outright.

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?

The phrase 'for missing guest orders' establishes the triggering scenario, and 'Does not reveal orders' steers the agent to the order tools when actual order data is wanted. There is no explicit 'use X instead' statement, so the routing is strong but inferred rather than spelled out.

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