Skip to main content
Glama

Fund a delivery

fund_delivery
Destructive

For deliveries created with fund=false, or after topping up the wallet. The delivery card shows these details: reply in one short line instead of repeating them.

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": {
      "delivery_id": "<delivery_id>"
    },
    "name": "fund_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnly=false, destructive=true, idempotent=false, and openWorld=true, so the safety profile is carried by structured data. The description adds nothing behavioral — it does not say the wallet is charged, whether funding is reversible, what happens on insufficient balance, or that a non-idempotent retry could double-charge. The second sentence is output-formatting advice, not behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only two sentences, but neither is a complete, front-loaded statement of the tool's action; the first is a subordinate clause with no main verb. The second sentence spends scarce description space on reply-style instructions rather than tool semantics, which is misallocated for a tool definition.

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

Completeness2/5

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

This is a destructive, non-idempotent, open-world mutation with no output schema and an undocumented parameter. For that complexity, the description leaves out cost source, failure modes, and return behavior, so an agent cannot safely invoke it beyond guessing the trigger condition.

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

Parameters1/5

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

With one parameter (delivery_id) and 0% schema description coverage, the description must compensate, yet it says nothing about which identifier is expected or where it comes from. The fragment only implies it is the delivery previously created with fund=false, which is thin and indirect.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what the tool does. It opens with an adverbial condition ('For deliveries created with fund=false, or after topping up the wallet') that only weakly implies paying for a delivery from wallet balance; the actual action must be inferred from the name and title. An agent knows the trigger situation but not the operation.

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 does give a concrete entry condition: use when a delivery was created with fund=false, or after a wallet top-up. That is real usage context. However, it names no alternatives among the many siblings (cancel_delivery, confirm_delivery, create_wallet_deposit) and states no exclusions or prerequisites such as sufficient balance.

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.