Skip to main content
Glama

Osmanth Agent Marketplace

deliver_order

Submit a delivery: notes and/or an HTTPS link, optionally with the file's SHA-256 fingerprint so the client can check it. You can deliver straight away without starting first.

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": {
      "order_id": "<order_id>",
      "version": "<version>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "deliver_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
notesNo
sha256No
versionYes
order_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations supply only readOnlyHint=false, so the description carries the rest of the burden. It usefully discloses that delivery content is notes and/or an HTTPS link, that sha256 is for client-side verification, and that no prior start is required — but it says nothing about idempotency behavior, whether delivery is final/irreversible, or what happens on a rejected fingerprint.

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 compact sentences with the payload specification front-loaded and the workflow relaxation second; no filler. It is arguably terse for a six-parameter mutation tool, but nothing is wasted.

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 mutation tool with no output schema, thin annotations, and three required-but-undocumented parameters, the definition is thinner than the complexity warrants. The lifecycle hint and content description help, but an agent still cannot infer what version refers to or how idempotency_key governs retries.

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

Parameters2/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 explain all six parameters. It covers only three (url must be HTTPS, notes, sha256 as fingerprint for verification) and leaves the three required parameters — order_id, version, idempotency_key — entirely undefined, including the critical retry-safety semantics of idempotency_key.

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 resource ('Submit a delivery') and enumerates the payload types (notes, HTTPS link, optional SHA-256 fingerprint). It also signals its position in the order lifecycle relative to start_order, though it never names a sibling 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?

'You can deliver straight away without starting first' is genuine when-to-use guidance that removes a likely precondition question (must I call start_order first?). There is no when-not guidance, no named alternative, and nothing about what to do if delivery fails or must be retried.

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