Skip to main content
Glama
Sign In

Ask Japan

by com.senpinai
OverviewDiscussionsAdmin

Get a restaurant menu

get_menu
Read-onlyIdempotent

Get a MARU Order restaurant's menu: categories, items with tax-included JPY prices, options (size, toppings), allergens and sold-out flags. Use list shop slugs from the maru://order/shops resource.

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": {
      "shop": "<shop>"
    },
    "name": "get_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
shopYesShop slug, e.g. maru-demo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral detail by stating that prices are tax-included JPY and that sold-out flags and allergens are included, which helps the agent interpret results.

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?

Two compact sentences, front-loaded with the tool's output contents and followed by the prerequisite for the single parameter. There is no wasted wording.

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

Completeness5/5

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

For a simple read-only, single-parameter tool with no output schema, the description sufficiently covers what the menu includes and where to get the required shop identifier. Nothing essential for correct invocation is missing.

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 meaning of the 'shop' parameter is already documented. The description adds practical value by saying where to obtain valid shop slugs (the maru://order/shops resource), which is not in the schema.

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?

It uses a specific verb and resource ('Get a MARU Order restaurant's menu') and immediately enumerates the menu contents: categories, items, JPY prices, options, allergens, and sold-out flags. An agent can understand exactly what this tool returns without consulting another schema.

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?

The description gives a clear prerequisite: use shop slugs from the maru://order/shops resource. It does not name exclusions or alternative tools, but for a single-purpose menu retrieval tool the key usage guidance is present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ask Japan toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources