Skip to main content
Glama

Canteen board

canteen_board
Read-onlyIdempotent

Free sample: https://apexfaucet.xyz/citizens/canteen/ ($0.001). Today on the Riverside Canteen board. Does not cook and does not read a wallet. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": "canteen_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world. The description adds value beyond them: price ($0.001 per call), accepted rails (USDC on Arc/Base/Solana, XNT on X1), the two-step terms-then-payment handshake, and the fact that payment settles inside the call. It does not disclose what content comes back or what the "terms" payload looks like.

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

Conciseness3/5

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

It is compact, but it front-loads a marketing URL and a "free sample ($0.001)" phrase that is self-contradictory and reads as promotion rather than capability. The core purpose sentence is buried mid-paragraph behind pricing detail.

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 required parameters, the description must carry the return-value burden, and it does not say what the board yields or how large/current that content is. Pricing and payment flow are fully covered, so the gap is limited to the payload itself.

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% and the schema already defines `payment` as a base64 x402 PAYMENT-SIGNATURE payload. The description goes further by explaining the empty-call-for-terms pattern that makes the parameter optional in practice, which the schema does not.

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

Purpose3/5

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

"Today on the Riverside Canteen board" plus a sample URL implies a paid daily content/board resource, and "does not cook" distinguishes it from a meal-ordering sibling. However, the description never states concretely what the board returns (menu? prices? listings?), so the verb+resource is only implied.

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?

It gives explicit procedural guidance: call once without `payment` to get terms, sign them with your own wallet, then call again with `payment` to complete. That is a clear how/when sequence. It stops short of naming alternatives or exclusions beyond "does not cook and does not read a wallet".

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