enquiry_fieldsEvery field of the Caravan Storage Prices 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 behavioral disclosure burden. It reasonably discloses what the tool provides and implies it is a read-only metadata lookup by directing actual submission to submit_enquiry. It could explicitly state that no data is submitted, but the description is not misleading.
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 a single, information-dense sentence that front-loads the core purpose and then enumerates the exact data elements included. Every phrase earns its place and there is no redundant or vague wording.
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?
Given the tool has no parameters, no annotations, and no output schema, the description supplies the necessary context: what the field list contains, how to use it, and how it connects to submission. Nothing critical is missing for an agent to invoke this 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 input schema is empty, so parameter documentation is not needed. The baseline of 4 applies because no parameter ambiguity exists.
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 what the tool exposes: every field of the Caravan Storage Prices enquiry, including key, label, type, required status, help text, and allowed options. It does not use an explicit verb like 'returns' or 'lists,' but the meaning is unambiguous and the relationship to submit_enquiry helps separate it from the submission tool.
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 actionable usage guidance: obtain the field definitions, then pass answers to submit_enquiry keyed by field key. This clarifies the intended workflow and distinguishes it from submit_enquiry, though it does not explicitly contrast with 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 has a separate role: one explains the overall purpose, one describes the input schema, and one submits the enquiry. There is no meaningful overlap between them.
All names are snake_case and clearly domain-related, but the pattern is mixed: 'enquiry_describe' and 'enquiry_fields' are noun-first, while 'submit_enquiry' is verb-noun. This is readable but not a fully consistent convention.
Three tools is well-scoped for a single enquiry-submission flow: orientation, schema discovery, and submission. Each tool earns its place.
The surface covers the full lifecycle of what is advertised: reading about the process, retrieving all editable fields, validating, and submitting with explicit consent. No obvious dead-end or missing operation exists.