Skip to main content
Glama
Sign In

KitchenGrade

by com.kitchengradeapp
OverviewDiscussionsAdmin

Search KitchenGrade Restaurants

search_restaurants
Read-onlyIdempotent

KitchenGrade searches captured Florida DBPR records for Lake, Orange, Osceola and Seminole counties only. This is not statewide coverage or a live statewide search. Use this tool only for an actual restaurant, public address or city search. Do not use it for MCP questions, documentation or connection tests, or send placeholder queries such as 'hello world' or 'model context protocol'. Use MCP ping for connection checks. Explain this coverage limit when a requested location is outside it or no record matches; zero results do not establish that a restaurant does not exist or has no inspections. Prefer a restaurant name as query and a separate city filter. Common requests such as 'find Winter Garden restaurants named Spoleto' are also supported. Returns exact identifiers and independently calculated, dated KitchenGrade inspection grades; not DBPR grades or food-safety guarantees. Empty results may include separately labeled nameSuggestions: possible close restaurant names that retain all submitted filters, not primary matches or a confirmed interpretation of the intended restaurant. Filter-recovery options instead explain which filters would need to change; those alternatives do not satisfy every original filter. Neither kind adds primary matches. Only describe recovery suggestions as nearby when nearRequestedCity is true, using the returned proximity qualification. Use an exact establishment ID with get_restaurant_grade before recommending a specific restaurant.

Input Schema

NameRequiredDescriptionDefault
cityNoOptional strict recorded-city filter within the covered counties, not a nearby radius. Omit it when searching the broader area; Orlando records do not match Winter Park. A city filter does not enable statewide coverage.
limitNo
queryYesPrefer just the restaurant name (e.g. Spoleto), public address or city text. Put the city in city when known. Common find/search for/look up/show me requests with a name and city are supported; arbitrary conversational instructions may need clarification. No personal data or coordinates. Do not send 'hello world', 'model context protocol', or other placeholder searches. MCP questions and connection tests are not restaurant searches. Use MCP ping for connection checks.
countyNoOptional filter within the covered counties only; it cannot expand coverage.
acceptable_onlyNoReturn only current A+, A, B grades; do not hide other grades when evaluating a supplied restaurant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Prefer just the restaurant name (e.g. Spoleto), public address or city text. Put the city in city when known. Common find/search for/look up/show me requests with a name and city are supported; arbitrary conversational instructions may need clarification. No personal data or coordinates. Do not send placeholder searches. Use MCP ping for connection checks."New value: +"Prefer just the restaurant name (e.g. Spoleto), public address or city text. Put the city in city when known. Common find/search for/look up/show me requests with a name and city are supported; arbitrary conversational instructions may need clarification. No personal data or coordinates. Do not send 'hello world', 'model context protocol', or other placeholder searches. MCP questions and connection tests are not restaurant searches. Use MCP ping for connection checks."
  2. Changed3 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"Optional strict recorded-city filter, not a nearby radius. Omit it when searching the broader area; Orlando records do not match Winter Park."New value: +"Optional strict recorded-city filter within the covered counties, not a nearby radius. Omit it when searching the broader area; Orlando records do not match Winter Park. A city filter does not enable statewide coverage."
    • changedInput schema / properties / county / description
      Previous value: -"Optional Florida county to disambiguate."New value: +"Optional filter within the covered counties only; it cannot expand coverage."
    • changedInput schema / properties / query / description
      Previous value: -"Restaurant name or public address/city text; no personal data or coordinates. Do not send placeholder searches. Use MCP ping for connection checks."New value: +"Prefer just the restaurant name (e.g. Spoleto), public address or city text. Put the city in city when known. Common find/search for/look up/show me requests with a name and city are supported; arbitrary conversational instructions may need clarification. No personal data or coordinates. Do not send placeholder searches. Use MCP ping for connection checks."
  3. Changed1 schema field changed
    • changedInput schema / properties / city / description
      Previous value: -"Optional city to disambiguate a location."New value: +"Optional strict recorded-city filter, not a nearby radius. Omit it when searching the broader area; Orlando records do not match Winter Park."
  4. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Restaurant name or public address/city text; no personal data or coordinates."New value: +"Restaurant name or public address/city text; no personal data or coordinates. Do not send placeholder searches. Use MCP ping for connection checks."
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses that coverage is limited to four counties and is not live or statewide, that zero results do not prove a restaurant does not exist, and that returned grades are independently calculated and dated rather than DBPR grades or safety guarantees. It further explains the semantics of nameSuggestions, filter-recovery options, and the nearRequestedCity proximity qualifier.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The coverage caveat is correctly front-loaded, but the prohibition on placeholder and MCP queries is restated twice in the description and again inside the query schema description, and 'not statewide coverage or a live statewide search' repeats the same idea. Several sentences earn their place, but the definition is noticeably longer than needed.

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?

There is no output schema, so the description carries the return-value burden and does so: exact identifiers, dated calculated grades, nameSuggestions versus filter-recovery options, and the proximity flag. For a filtered search tool with a mandatory handoff to get_restaurant_grade, nothing an agent needs to call or interpret results is missing.

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 already 80%, and the description adds real meaning on top: city is a strict recorded-city filter, not a nearby radius (Orlando does not match Winter Park), and a city filter cannot expand coverage. The remaining parameters (limit, county, acceptable_only) are left entirely to the schema, which is acceptable given its enum and default documentation.

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?

States a specific verb and resource (searches captured Florida DBPR restaurant records) plus a hard scope boundary (Lake, Orange, Osceola and Seminole counties only, not statewide). It also explicitly differentiates from its sibling by telling the agent to use an exact establishment ID with get_restaurant_grade before recommending a restaurant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use (actual restaurant, address or city searches; 'find Winter Garden restaurants named Spoleto'), explicit when-not (MCP questions, documentation, connection tests, placeholder queries) and names the correct alternative (MCP ping). It also prescribes the preferred calling pattern: restaurant name as query with city as a separate filter.

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

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