Aclimação

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

Name	Required	Description	Default
`limit`	No	Max dishes to return (default 20, max 50).
`query`	No	Dish 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?

No annotations provided, but description discloses behavior: searches all menus across restaurants, groups by dish, returns price/description/dietary labels/URL. Implies read-only, no destructive effects. Transparent about output structure.

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?

Two sentences with no wasted words. Purpose is front-loaded. Efficient and clear.

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?

No output schema, but description covers return values (price, description, dietary labels, URL). With two well-described parameters and clear purpose, it is sufficiently complete for a search tool.

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%, baseline 3. Description adds value by explaining query is a dish name and that omitting it lists top dishes. Also explains limit defaults and max, supplementing 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?

Description clearly states the tool finds restaurants serving a dish, with specific verb and resource. It distinguishes from siblings like search_places by focusing on dish-level search. Example query 'feijoada' makes it concrete.

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?

Explicitly states use for 'where can I eat X' questions. Mentions omitting query to list top dishes, giving clear usage context. Does not explicitly state when not to use, but clues are sufficient.

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

All Aclimação tools Inspect

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 targets a distinct domain (booking, events, places, food, movies, etc.) with clear boundaries. Even similar actions like reservations are clearly differentiated by context (booking appointment vs. table vs. event tickets vs. RSVP).

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_events, search_places). No mixing of conventions or vague verbs.

Tool Count4/5

28 tools is on the higher end but justifiable for a comprehensive neighborhood directory covering bookings, events, store, reviews, FAQs, guides, offers, movies, and more. Each tool serves a specific purpose without redundancy.

Completeness4/5

The tool surface covers the main user workflows (searching places, booking services, events, food ordering, loyalty, reviews). Minor gaps like lack of user account management or direct payment handling are acceptable for a directory MCP.

Resources

Need Help?