enquiry_fieldsEvery field of the Forklift Course Finder enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden. It discloses what fields are included and qualifies options with 'where there are any', giving a good sense of the return content. However, it never explicitly says the tool is read-only or what the output shape looks like beyond the attribute list.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no filler. The description front-loads the resource and then immediately lists the useful attributes and the relationship to submit_enquiry.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, simple introspection tool with no output schema, the description is complete: it specifies exactly what data will be returned and how that data is meant to be used with the sibling submit_enquiry tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the schema and description have no parameter semantics to document; the 0-param baseline is 4. The sentence about passing answers keyed by field key is not parameter documentation for this tool, but it does contextualize the returned keys.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource as 'Every field of the Forklift Course Finder enquiry' and enumerates the returned attributes (key, label, type, required, help text, allowed options). It does not use an explicit verb like 'list' or 'get', and it does not contrast with the sibling enquiry_describe, so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context by telling the agent that answers should be passed to submit_enquiry keyed by field key, which implies when this tool is useful. It does not explicitly state when to use enquiry_describe instead, so it lacks the explicit exclusion needed for a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct role: one explains the process, one returns the field schema, and one performs the submission. There is no overlap in purpose.
All names are lowercase snake_case and readable, but the pattern is slightly mixed: two use an enquiry_ prefix while the third leads with the verb submit_. This is a minor deviation from a fully uniform convention.
Three tools is well-scoped for the narrow workflow of describing, inspecting, and submitting an enquiry. Each tool earns its place without redundancy.
The surface fully covers the enquiry workflow: schema discovery, validation preview, and two-step submission with confirmation token. No obvious missing operations for this domain.