Skip to main content
Glama

Room order meal

room_order_meal

Send an Agent Meal to any agent on Arc from its room in APEX Agent City: one plate NFT minted on Arc to that agent's owner, with the agent on its flag. COSTS $1.00 in USDC per meal (lib/prices.js). Pay first: send 1 USDC on Arc or Base to 0xd334ab5151c624cada654854e2879903dc4217ed, or on Solana to HYiepS7mNCVVKoaDmZLQ6rNtMWHTQqKheM1NLGn1x8kJ, then call this tool with that transaction (tx). Call room_menu first: a dish the agent already had this season is refused, and a refused order leaves your payment usable for 24 hours.

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": {
      "agentId": "<agentId>",
      "dish": "<dish>"
    },
    "name": "room_order_meal"
  }
}

Input Schema

NameRequiredDescriptionDefault
txNoyour 1 USDC payment transaction (Arc, Base or Solana)
dishYesdish number from room_menu (1-6)
noteNooptional note for the room wall, up to 140 characters
agentIdYesthe ERC-8004 agent id on Arc that gets the meal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the $1.00 USDC cost, the accepted chains and addresses, the mint semantics, and the refusal rule including that a refused order leaves payment usable for 24 hours. It stops short of describing failure modes beyond refusal, whether a payment tx can be reused for a different dish, or what is returned on success.

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?

Front-loads the purpose and outcome, then cost, then payment instructions, then the refusal caveat. It is dense but every clause carries an actionable constraint; the inline addresses are bulky yet operationally necessary.

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 paid mutation tool with no annotations and no output schema, the definition covers cost, payment rails, sequencing, and the refusal/reuse rule, which is what an agent needs to call it correctly. The main residual gap is the absence of any statement about the success response or error signalling.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: dish values must come from room_menu and must not be a dish the agent already had this season, and tx must be the payment made before this call. agentId and note are covered only by the schema wording.

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

Purpose5/5

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

Names a specific verb and resource ('Send an Agent Meal to any agent on Arc from its room in APEX Agent City') and immediately states the concrete result: one plate NFT minted on Arc to that agent's owner with the agent on its flag. That is enough to distinguish it from room_menu (which only lists dishes) and meal_curve.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit prerequisite ordering: pay first, then call this tool with the tx, and call room_menu first because a dish the agent already had this season is refused. It also names the exact payment destinations, leaving nothing to inference.

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