NUM

Get place details and how to book it

num_get_place

Read-onlyIdempotent

Full record for one place, by the place_id that num_search_places returned, including HOW TO BOOK IT on the venue's own terms. booking.method is one of: request (the venue takes requests through NUM and confirms each one itself), venue_system (send the traveller to booking.url, prefilled when you pass party_size, date and time), phone (the number is for the traveller to call), not_through_num, closed, unknown. Follow booking.guidance exactly. If open_status.closed is true, NUM holds evidence the place has gone: do not send anyone there. accolades carry their source; menu is the owner's own list and prices. Each call counts against the daily read quota.

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": {
      "place_id": "<place_id>"
    },
    "name": "num_get_place"
  }
}

Input Schema

Name	Required	Description
`date`	No	Optional: YYYY-MM-DD, to prefill the venue's booking page.
`time`	No	Optional: HH:MM 24-hour, local to the venue.
`place_id`	Yes	The place_id returned by num_search_places.
`party_size`	No	Optional: people in the party, to prefill the venue's booking page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 26, 2026

addedInput schema / properties / date

Added value: +{
+  "description": "Optional: YYYY-MM-DD, to prefill the venue's booking page.",
+  "type": "string"
+}

addedInput schema / properties / party_size

Added value: +{
+  "description": "Optional: people in the party, to prefill the venue's booking page.",
+  "maximum": 40,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / time

Added value: +{
+  "description": "Optional: HH:MM 24-hour, local to the venue.",
+  "type": "string"
+}

First observedAug 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavior beyond annotations: each call counts against the daily read quota, booking.method meanings and how to act on them, the closed-status caution, and that accolades carry source and menu is owner-provided. No contradiction with annotations.

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?

The description is moderately long but every sentence carries functional weight. It front-loads the core purpose and then unpacks booking details and precautions in a logical order. Slightly dense but not verbose; no filler.

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?

With no output schema, the description compensates by explaining the return structure's key aspects: booking.method values, open_status.closed, accolades, and menu. It also flags the quota. It doesn't enumerate every field, but for a get-by-id tool it's sufficient for an agent to understand expectations and side effects.

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 parameters are already documented. The description adds meaning by explaining that party_size, date, and time are used to prefill the venue's booking page, and that place_id comes from num_search_places. This bridges the parameters to the booking workflow, adding value beyond 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?

The description clearly states the tool returns the full record for one place by place_id from num_search_places, and explicitly includes how to book it. The verb+resource (get place details) is specific, and it differentiates itself from siblings like num_search_places (search) and num_submit_* (submissions). It even details booking.method values, making the purpose unmistakable.

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 implies the workflow (use after num_search_places) and provides strong usage guidance: how to interpret booking.method, when to send travellers (and when not to, e.g., if open_status.closed is true), and to follow booking.guidance exactly. It doesn't explicitly name alternative tools or state when not to use this one, but the context is clear enough for an agent.

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

All NUM tools Inspect

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.