Fluefold: Coordinated kitchen exhaust cleaning for restaurant groups

Describe a need to Fluefold in words

interpret_requirement

Give Fluefold the buyer's requirement, or a correction or addition to it, in their own words: it is read into a structured requirement (each value says which words it came from), conflicting or unclear facts come back as one question, and words not yet read are kept as written. Pass the requirement (id, token) from the first answer to continue it. Nothing is sent or ordered: send_requirement sends it when the buyer says so. When you already have the fields in structured form, use submit_request instead.

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": {
      "utterance": "<utterance>"
    },
    "name": "interpret_requirement"
  }
}

Input Schema

Name	Required	Description
`turn_id`	No	Your id for this message: a retry with the same id is applied once
`timezone`	No	The buyer's IANA time zone, for reading dates
`utterance`	Yes	The buyer's words, as written
`requirement`	No	The requirement to continue

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say it is not read-only and not open-world; the description goes further and clarifies that nothing is sent or ordered despite the write-like flag, that conflicts come back as a single question, and that unread words are preserved verbatim. It also discloses the provenance behavior (each value records which words it came from), which is not inferable from annotations.

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?

The purpose is front-loaded and every clause carries information, but the opening sentence is heavily compound, stacking four behaviors with colons and parentheses. Slightly denser than ideal, though nothing is pure 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?

For a four-parameter tool with a nested continuation object and no output schema, the description covers what happens on return (structured requirement with provenance, an ambiguity question, retained raw words) plus the send boundary. An agent has enough to call it correctly on the first turn and on continuations.

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%, so the baseline is 3, but the description adds workflow meaning beyond the schema: the requirement object (id, token) is explicitly the handle from the first answer used to continue the same requirement, and utterance is framed as the buyer's own words. It does not add detail on timezone or turn_id beyond the schema text.

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 uses a specific verb and resource ('Give Fluefold the buyer's requirement... in their own words') and states the transformation performed (read into a structured requirement). It also names two siblings it is not (send_requirement, submit_request), so an agent can distinguish it without opening any schema.

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?

Explicit routing rules are given: use this for a requirement, correction, or addition in prose; use submit_request when the fields are already structured; use send_requirement when the buyer authorizes sending. It also states the continuation precondition (pass id and token from the first answer).

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

All Fluefold: Coordinated kitchen exhaust cleaning for restaurant groups tools Inspect

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

Need Help?