Skip to main content
Glama

NYCfoodie

by app.railway.up.nycfoodie-production
OverviewDiscussionsAdmin

find_guides

Read-only

Find curated editorial guides (ranked lists) matching a theme, e.g. 'best ramen'. Returns each guide with its ranked entries, blurbs and linked restaurants. Use when the user wants the editorial lists themselves rather than individual restaurant picks. Set include_entries=false to list guide titles and metadata without pulling every entry blurb.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYesCity slug, always required. Currently 'new-york', covering the five boroughs plus the immediate metro (within 30 km of Manhattan).
limitNoMax results (default 10)
queryNoTheme, e.g. 'best ramen', 'date night'
include_entriesNoSet false to return guide metadata without the ranked entry blurbs (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"City slug, always required. Currently 'new-york'."New value: +"City slug, always required. Currently 'new-york', covering the five boroughs plus the immediate metro (within 30 km of Manhattan)."
    • addedInput schema / properties / include_entries
      Added value: +{
+  "description": "Set false to return guide metadata without the ranked entry blurbs (default true)",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds behavioral detail beyond that: the tool returns ranked entries with blurbs, and include_entries=false changes the response to guide metadata only. This helps the agent predict output behavior without overpromising.

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?

Three focused sentences: purpose with an example, usage guidance, and a practical parameter tip. Every sentence earns its place 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.

Completeness4/5

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

The description adequately describes the return content (ranked entries, blurbs, linked restaurants), the optional response mode via include_entries, and when to use the tool. With no output schema, this is sufficient for a read-only query tool, though it could mention pagination or ordering behavior.

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?

Schema description coverage is 100%, so the schema already documents all parameters well. The description adds a little extra context, especially for include_entries, but does not substantially enrich parameter meaning beyond what the schema provides.

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 states a specific verb and resource ('Find curated editorial guides'), explains what it returns (ranked entries, blurbs, linked restaurants), and distinguishes itself from sibling tools by explicitly contrasting with 'individual restaurant picks'.

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 explicitly says when to use the tool: 'Use when the user wants the editorial lists themselves rather than individual restaurant picks.' It does not name alternative sibling tools or provide when-not-to-use exclusions, but the usage context is clear.

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

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