enquiry_fieldsEvery field of the Office Relocation Quotes 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 provided, the description carries the full burden of behavioral disclosure. It discloses the exact content of the tool's output: key, label, type, required status, help text, and available options. It implicitly indicates a read-only metadata operation, though it does not explicitly state side-effect-free behavior.
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?
The description is two sentences with no filler. The first sentence enumerates the fields of the returned metadata, and the second provides a direct usage instruction tying the output 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, low-complexity metadata tool, the description is complete: it specifies what the tool returns, lists the returned attributes, and explains the downstream use case with submit_enquiry. No additional context is needed for an agent to call or interpret the tool correctly.
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 the schema description coverage is effectively complete, so there is no parameter documentation burden. The description still adds value by explaining the role of field keys when constructing submit_enquiry calls.
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 states that this tool provides every field of the Office Relocation Quotes enquiry, and enumerates the attributes included: key, label, type, required flag, help text, and allowed options. It is distinguished from submit_enquiry by explicitly pointing to that sibling as the place to pass the answers, though it does not differentiate from enquiry_describe.
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 second sentence gives practical guidance: use the field keys from this tool to key answers to submit_enquiry. However, it does not explicitly state when to use this tool versus enquiry_describe, or any conditions that would make one preferable over the other.
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 purpose: one explains the process, one provides the schema, and one performs the submission. There is no overlap or risk of selecting the wrong tool.
Names are readable and share the 'enquiry' concept, but they follow mixed patterns: 'enquiry_describe' is noun-verb, 'enquiry_fields' is noun-noun, and 'submit_enquiry' is verb-noun. A more consistent set would use 'describe_enquiry', 'get_enquiry_fields', and 'submit_enquiry'.
Three tools is well-scoped for a focused enquiry-submission server. Each tool covers an essential step in the workflow without redundancy.
The surface fully covers the enquiry lifecycle: understanding the process, retrieving the required fields, and submitting with two-step confirmation. No additional CRUD operations are necessary for this domain.