Skip to main content
Glama

KnownGate

by com.knowngate

check_venue

Read-only

Rule a whole venue's published chart against the household restrictions in one call. Needs a key (Authorization: Bearer kg_live_…); create a free one with the register tool. Returns per-verdict counts, the most severe items, the operator's cross-contact caveat verbatim, and the chart's source and read date. A venue with no machine-readable chart says so honestly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
venueYes
restrictionsYesHousehold restrictions. FDA-9 keys ("peanut", "sesame", "milk", …) as strings, or { key, note } when a note matters (e.g. { key: "tree_nut", note: "cashew" }). May be empty when thresholds carry the premise.

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint, it discloses the required bearer key, the return payload (counts, severe items, cross-contact caveat, source/read date), and the edge-case behavior for venues without machine-readable charts. These are meaningful behavioral traits not visible in annotations or schema.

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 sentences front-load the primary action, then cover auth, return contents, and an important edge case. Every sentence adds information without repetition or filler.

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?

Given no output schema, the description usefully enumerates what will be returned and states what happens when a chart is unavailable. Combined with the input schema and readOnly annotation, an agent has enough context to select and call the tool.

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?

The description maps 'venue' and 'restrictions' conceptually but adds little structural detail beyond the schema, which already documents the restrictions array and location. With only 50% schema description coverage, it could have compensated more for the venue object's name field, though the core intent is clear.

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 opening sentence names a specific action—'Rule a whole venue's published chart against the household restrictions'—with a clear resource and scope. The phrase 'whole venue' and 'in one call' distinguishes this from item- or plan-level siblings.

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 gives clear context for use—batch auditing a venue's full chart against restrictions—and even directs users to register for a key. It does not explicitly say when to prefer check_item or check_plan, so it stops short of full exclusion guidance.

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

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

check_item, check_plan, and check_venue are cleanly separated by scope: a single food, a batch/plan up to 25 items, and a venue-level chart. register is clearly the auth/key-creation step and cannot be confused with the checking operations.

Naming Consistency4/5

The three core tools follow a consistent check_<noun> snake_case pattern, which makes their behavior predictable. register is a clear, conventional name but breaks the verb_noun pattern, so the set is not perfectly uniform.

Tool Count5/5

Four tools is a well-scoped set for this server: one necessary registration step plus three checking operations at increasing levels of granularity. Each tool has a distinct purpose and nothing feels redundant or bloated.

Completeness4/5

The checking surface is essentially complete: single items, composite plans, and venue charts are all covered, and register provides the required key. The only notable gap is that household premise/restriction configuration is not exposed through MCP, so agents must rely on that being set up outside the server.

Resources