enquiry_fieldsEvery field of the Employee Cost Calculator NZ 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?
With no annotations, the description carries the behavioral disclosure burden. It openly describes this as a metadata retrieval operation listing all field attributes and implies no side effects, though it does not explicitly state that the call is read-only or has no auth requirements.
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 concise sentences, each earning its place. The first defines the output contents, and the second gives the key relationship to submit_enquiry. No filler or repeated schema information.
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 an input-free metadata tool, the description is mostly complete: it enumerates the field attributes returned and explains how to use the output. It does not specify the exact return container, but the absence of parameters and output schema makes this a minor gap.
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 has zero parameters and an empty input schema, so parameter semantics are not applicable. The description still adds value by explaining that returned field keys are used to key answers for submit_enquiry.
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 names the exact resource, 'Every field of the Employee Cost Calculator NZ enquiry', and lists precisely what is returned: key, label, type, required status, help text, and allowed options. It also ties the output to submit_enquiry, distinguishing it from the sibling tools.
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 clearly signals when this tool is useful: to obtain field keys so answers can be passed to submit_enquiry. It does not explicitly contrast against enquiry_describe, but the usage context is transparent and actionable.
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 targets a distinct concern: running the calculator, explaining the calculator, explaining the enquiry workflow, listing enquiry fields, and submitting the enquiry. The only potentially adjacent pair is enquiry_describe and enquiry_fields, but their descriptions draw a clear line between process and schema.
Names are readable and grouped by function, but they mix conventions: calculate and submit_enquiry are verb-first, while calculator_describe and enquiry_describe are noun-first, and enquiry_fields is a noun phrase. No single pattern is sustained across the set.
Five tools is an appropriate size for a focused site with two features: a calculator and an enquiry flow. Each tool has a clear role, and there are no redundant or filler tools.
The calculator surface is complete with run and describe tools, and the enquiry surface covers workflow, schema, and two-step submission. The two-step confirmation is handled inside submit_enquiry, so there are no missing lifecycle steps.