enquiry_fieldsEvery field of the Florida Roof Replacement 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 burden of explaining behavior. It discloses the contents of the returned field metadata and implies a read-only informational operation, but it does not explicitly state response format, absence of side effects, or any limitations/errors. This is adequate for a simple metadata getter but not richly transparent.
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 tight sentences with no filler. It front-loads the core purpose ('Every field...') and adds a directly actionable downstream note. Every phrase 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?
For a no-parameter metadata tool, the description covers what is returned, the data attributes, and how to use the output with a sibling tool. It is slightly incomplete only in not clarifying the relationship, if any, with enquiry_describe.
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, so the baseline is 4. The description adds relevant context by explaining how the returned field keys should be used when calling submit_enquiry, which is more useful than the empty schema alone.
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 Florida Roof Replacement Cost enquiry, listing the exact attributes (key, label, type, required, help text, options). It identifies the resource and the kind of data, but it does not explicitly differentiate itself from the sibling enquiry_describe, so it stops short of full distinction.
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 provides actionable usage guidance by telling the agent to pass answers to submit_enquiry keyed by field key. This gives clear context for how the output should be used downstream, though it does not explicitly state when to use this tool instead of enquiry_describe.
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 covers a distinct aspect of the same enquiry flow: describing the behaviour, providing the field schema, and submitting with confirmation. There is no meaningful overlap or ambiguity between them.
The 'enquiry_' prefix gives some cohesion, but the convention is mixed: 'enquiry_describe' is noun-verb, 'enquiry_fields' is noun-noun, and 'submit_enquiry' is verb-noun. The names are readable but not consistently structured.
Three tools is exactly right for this narrow, single-purpose server. Each tool earns its place and there is no unnecessary surface area.
For the stated purpose of submitting an enquiry, the set covers the full flow: understanding what happens, retrieving the required fields, and submitting with consent/confirmation. No obvious lifecycle gaps exist for this scope.