Skip to main content
Glama

Read my menu

get_my_menu
Read-onlyIdempotent

Use when the venue owner wants to see or check their current menu: categories, products, prices, availability and allergens, with the ids needed for later changes. Requires the owner to connect their PRENOTO account. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
venue_idNoOptional. Only needed when the account manages several venues (see list_my_venues).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint and openWorldHint, so the bar is lower; the description still adds real value by disclosing the account-connection prerequisite and the fact that returned ids enable later changes. It does not discuss pagination or result size, but for a small read tool that is minor.

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?

One front-loaded sentence with the trigger first and the return contents second, followed by a short prerequisite and a one-word mode note. The trailing 'Read-only.' largely restates readOnlyHint and is the only wasted token.

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?

There is no output schema, and the description compensates by listing the fields a caller will receive plus the id values needed downstream. Combined with the auth prerequisite, an agent has enough to call this correctly; only multi-venue disambiguation is left to the schema.

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

Parameters3/5

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

With one optional parameter at 100% schema coverage, the schema already documents venue_id as optional and points at list_my_venues. The description adds only the implicit notion of account-level scoping ('the account manages several venues' context), which is already present in the schema, so baseline 3 applies.

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 and resource ('see or check their current menu') and enumerates the contents returned (categories, products, prices, availability, allergens, ids). It is clear what the tool does, but it never names a sibling such as get_menu_format or about_prenoto_menu to say what this is not.

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?

'Use when the venue owner wants to see or check their current menu' gives a concrete triggering context, and the prerequisite (owner must have connected their PRENOTO account) is stated explicitly. There is no explicit when-not or named alternative, so it falls short of full routing guidance.

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