Skip to main content
Glama

List allergen-free venues

list_allergen_free
Read-onlyIdempotent

Rank Sydney venues by how many dishes are free of one allergen (free by default, or able to be made free), optionally within a region or suburb and for one kind of dish. Examples: family 'gluten' in 'Northern Beaches'; family 'nuts' with dish_type 'dessert'; family 'dairy' in 'Inner West' with dish_type 'pasta'. Returns venues with their counts, links and the day each menu was read, plus example dishes when a dish type is given.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "family": "<family>"
    },
    "name": "list_allergen_free"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoVenues to return. Default 10.
familyYesThe allergen: gluten (coeliac), dairy, nuts, peanut, treenut, egg, soy, sesame, shellfish, fish, seafood, lupin, sulphite; or the diets vegetarian, vegan.
regionNoOptional. A Sydney region or suburb: 'Northern Beaches', 'Inner West', 'Parramatta', 'Manly'.
dish_typeNoOptional. A kind of dish: pasta, pizza, burger, sandwich, salad, soup, curry, noodles, dumplings, sushi, rice, steak, seafood, breakfast, dessert, ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that: it defines the counting rule ('free by default, or able to be made free'), states results are ranked by count, and discloses return contents including links and the day each menu was read — useful given there is no 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.

Conciseness4/5

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

Purpose is front-loaded in the first clause, examples follow, and return behavior closes it out — a logical order with no filler. The example list is somewhat repetitive but each demonstrates a different parameter combination, so it earns most of its space.

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?

With four fully documented parameters and no output schema, the description carries the burden of explaining results and does so (counts, links, menu-read date, sample dishes). Ranking semantics for ties or the meaning of 'counts' relative to dish_type are the only small gaps.

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 coverage is 100%, so every parameter already carries its own description including the allowed family values. The description reinforces the single-allergen constraint and shows combinations in the examples, but adds little syntax or format detail beyond the schema. Baseline 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 opens with a specific verb and resource ('Rank Sydney venues by how many dishes are free of one allergen') and states scope constraints (single allergen, optional region/suburb, optional dish type). This is clearly distinguishable from siblings like get_venue (single venue) or search_dishes (dish-centric).

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?

Three concrete example invocations ('gluten' in 'Northern Beaches', 'nuts' with 'dessert', 'dairy' in 'Inner West' with 'pasta') give a clear sense of when this tool fits. There are no explicit exclusions or pointers to alternatives such as compare or search_dishes, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources