Skip to main content
Glama

consume

Eat or drink a Food Cart item you own and see its effect. itemId accepts your inventory row id or its foodItemId (catalog ID). Requires a UUID requestId.

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": {
      "requestId": "<requestId>",
      "itemId": "<itemId>"
    },
    "name": "consume"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that the item is consumed/destroyed and that an effect is returned, which is useful. However, it says nothing about irreversibility, inventory failure modes, or what requestId actually guarantees (idempotency/retry safety) — a notable gap for a mutation tool with zero annotation coverage.

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 short sentences with the action and its result front-loaded, then the one genuinely ambiguous parameter, then the required-id note. No filler and nothing out of order.

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?

With no output schema and no annotations, the description should explain the return shape ('see its effect' is vague — buffs? healing? stat deltas?) and the consequences of the mutation. It covers inputs adequately but leaves the outcome underspecified for a state-changing tool.

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?

Schema description coverage is 0%, so the description must compensate, and it does for the harder parameter: itemId accepts either an inventory row id or a foodItemId catalog id, which the schema's plain string type does not convey. requestId is only described as "a UUID", which the schema's format/pattern already state, and its idempotency semantics are left unexplained.

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 pair and resource: "Eat or drink a Food Cart item you own and see its effect." That is far more specific than the bare name 'consume', and the Food Cart scoping separates it from cook/brew. It never names the nearest sibling, drink_potion, so an agent must infer the boundary between consuming a cart item and drinking a potion.

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?

Ownership ("an item you own") implies the prerequisite and the general situation, but there is no explicit when-to-use/when-not and no routing to alternatives such as drink_potion or cook. Usage is inferable but not stated.

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