Skip to main content
Glama

NUM

by com.itsnum
OverviewDiscussionsAdmin

Search places

num_search_places
Read-onlyIdempotent

Search NUM's travel directory: more than 2.5 million places — restaurants, bars, hotels, spas, tours and shops, deepest in Thailand and the UK. Say where to look: city (one of NUM's destinations — see num_list_destinations) or country; then narrow with q, area and category. Places NUM knows have closed are never returned. Returns name, category, address, phone, website, coordinates and whether the owner has claimed the listing; call num_get_place for how to book one. Each call counts against the daily read quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree text matched against the place name.
areaNoA neighbourhood inside the destination, e.g. 'Kata' or 'Soho'.
cityNoA NUM destination, e.g. 'Phuket', 'Edinburgh', 'Bangkok', 'London'. Required unless country is given.
limitNoMax results, default 20, cap 50.
countryNoISO-2 code or name, e.g. 'TH' or 'Thailand'. Searches every NUM destination in that country.
categoryNoe.g. 'Restaurant', 'Bar', 'Hotel', 'Spa', 'Tour'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / area
      Added value: +{
+  "description": "A neighbourhood inside the destination, e.g. 'Kata' or 'Soho'.",
+  "type": "string"
+}
    • changedInput schema / properties / city / description
      Previous value: -"City or destination, e.g. 'Phuket', 'Edinburgh', 'Bangkok', 'London'."New value: +"A NUM destination, e.g. 'Phuket', 'Edinburgh', 'Bangkok', 'London'. Required unless country is given."
    • changedInput schema / properties / country / description
      Previous value: -"ISO-2 country code, e.g. 'TH' or 'GB'."New value: +"ISO-2 code or name, e.g. 'TH' or 'Thailand'. Searches every NUM destination in that country."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark the operation read-only, open-world, idempotent, and non-destructive. The description adds meaningful behavioral context beyond those: closed places are never returned, each call counts against the daily read quota, and it enumerates the exact fields returned, compensating for the lack of an output schema.

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?

The description is dense but well organized: scope, how to search, a filtering caveat, return contents, next-step routing, and quota impact are each covered in compact sentences. No words are wasted and the most important information is front-loaded.

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 search tool with no output schema, the description is remarkably complete: it covers data scope, required location inputs, narrowing parameters, closed-place behavior, return fields, the follow-up tool, and quota impact. The limit parameter is fully documented in the schema, so its absence from the description is not a gap.

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?

The input schema already provides 100% coverage for all six parameters with clear descriptions. The main text reinforces the relationship between city and country and describes q/area/category as narrowing filters, but it does not add substantial parameter semantics beyond what the schema already states, so the baseline of 3 is appropriate.

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 searches NUM's travel directory of places, names the categories included, and differentiates it from siblings by pointing to num_get_place for booking and num_list_destinations for valid city choices. The verb 'search' plus the explicit resource leaves no ambiguity about what this tool does.

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 a concrete usage recipe: specify a city or country first, then narrow with q, area, and category. It also routes the agent to relevant siblings, though it does not explicitly state when to avoid this tool in favor of submission-oriented siblings, which are clearly different actions.

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

All NUM 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