enquiry_fieldsEvery field of the Sponsor Licence 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 provided, the description carries the behavioral burden. It discloses what the response will contain and notes that options are included only where they exist. It implies a read-only metadata operation and is transparent about output composition, though it does not discuss errors or authentication.
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 sentences with no filler: the first front-loads what the tool returns, and the second adds the essential connection to submit_enquiry. Every part 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 zero-parameter metadata-listing tool, this is complete: it specifies the output fields and how to use them afterward. Since there is no output schema, enumerating the field attributes is especially valuable.
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 takes zero parameters and schema coverage is effectively complete, so no parameter explanation is needed. The description appropriately focuses on the response structure rather than parameter details.
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 the resource ('Sponsor Licence Cost enquiry') and lists the exact contents returned (key, label, type, required, help text, options). It distinguishes itself from submit_enquiry by explaining that answers should be keyed by field key, though it does not explicitly contrast with 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 description gives clear usage context: call this tool to obtain the field keys needed for submit_enquiry. It does not explicitly mention when not to use it or compare with enquiry_describe, but the intended workflow is concrete and easy for an agent to follow.
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: enquiry_describe explains the process, enquiry_fields provides the exact schema, and submit_enquiry handles the actual two-step submission. There is no meaningful overlap or ambiguity between them.
The names are all snake_case and readable, but the pattern is mixed: enquiry_describe and enquiry_fields use a noun-first structure while submit_enquiry uses verb-first. Still, the shared 'enquiry' theme makes the set understandable.
Three tools perfectly cover the narrow workflow: discover the process, inspect the required fields, and submit the enquiry. No tool feels redundant and none is missing for the stated purpose.
The tool set covers the full enquiry journey from orientation through field discovery to validated submission with consent and confirmation. Since this server is scoped to one specific enquiry type, no additional CRUD operations are needed.