enquiry_fieldsEvery field of the Lease Renewal Cost 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 full burden. It discloses what the tool returns (field metadata) and implies a read-only metadata lookup. It also notes that allowed options are included only 'where there are any', giving useful nuance about variable output content.
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, the first front-loading the resource and attributes, the second adding a direct usage instruction. No filler words; every sentence earns its place.
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?
The description sufficiently explains the return content and how to use it with submit_enquiry. Given the tool's simplicity and lack of output schema, it does not need to explain errors or ordering. Slightly more explicit return structure (e.g., an array of field objects) could push it higher, but it is complete enough for an agent to invoke 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 input schema is empty and there are zero parameters, so the description bears no parameter-explanation burden. Baseline for zero parameters is 4, and the description appropriately stays focused on output rather than inventing parameter guidance.
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 the tool returns every field of the Lease Renewal Cost enquiry, listing the exact attributes (key, label, type, required, help text, options). It differentiates from submit_enquiry by explaining that answers should be keyed by field key, but it does not explicitly differentiate from sibling 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?
It provides clear context: the tool exposes fields for the Lease Renewal Cost enquiry, and the output should be used to key answers when calling submit_enquiry. It does not offer explicit exclusions or compare against enquiry_describe, but the usage relationship is made concrete.
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 provides the schema, one handles submission. The descriptions reinforce the separation, including explicit guidance on which tool to call first.
The naming is readable but not fully consistent: 'submit_enquiry' follows verb_noun, while 'enquiry_describe' reverses the order and 'enquiry_fields' is noun_noun. A more uniform pattern like describe_enquiry, get_enquiry_fields, submit_enquiry would improve consistency.
Three tools is well-scoped for a single enquiry workflow: explain, define fields, submit. Each tool earns its place without redundancy or unnecessary surface area.
The surface fully covers the enquiry lifecycle: understanding the process, retrieving field definitions, and submitting with a two-step confirmation and consent handling. No obvious dead ends or missing operations for the stated purpose.