Skip to main content
Glama

Tatuapé

by io.github.junoventures

search_dishes

Find which restaurants serve a dish in this neighborhood. Searches every menu item across all restaurants on the site, grouped by dish — e.g. query "feijoada" returns each restaurant serving it with price, description, dietary labels, and the place URL. Omit the query to list the most-served dishes. Use this for any "where can I eat X" question.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax dishes to return (default 20, max 50).
queryNoDish name or part of it, e.g. "feijoada", "pizza margherita". Omit to list top dishes.

TDQS

A4.4/5.0
Behavior4/5

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

The description details the search scope (all restaurants, grouped by dish), returned fields (price, description, dietary labels, URL), and behavior without query. With no annotations, it covers key behavioral aspects.

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 two sentences plus a usage instruction, no wasted words, front-loaded with core purpose.

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?

Covers purpose, usage, parameters, output format. Does not explain how 'neighborhood' is determined from context, but overall sufficient for agent use.

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 descriptions cover 100% of parameters. The description adds meaning: explains 'query' as a dish name, that omitting it lists top dishes, and results are grouped. Adds value beyond 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's purpose: 'Find which restaurants serve a dish in this neighborhood.' It specifies the verb 'find' and the resource 'dishes' grouped by restaurant, distinguishing it from siblings like search_places.

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?

Explicit guidance is given: 'Use this for any "where can I eat X" question.' Also explains behavior when omitting query. No mention of when not to use or alternatives, but context is provided.

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

All Tatuapé toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose, even among similar actions like booking, reservation, and ticket purchase—their descriptions clarify the domain and flow. No two tools could reasonably be confused.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_blog_posts). There are no deviations or mixed conventions.

Tool Count3/5

At 28 tools, the surface is larger than ideal for a single server, but each tool covers a distinct feature of the neighborhood directory (bookings, events, store, etc.). It borders on heavy but is still manageable for an agent.

Completeness5/5

The tool set covers the full lifecycle of browsing and acting on a neighborhood directory: search, details, reviews, menus, events, booking, reservations, store, loyalty, and more. No obvious gaps exist for the intended use case.

Resources