enquiry_fieldsEvery field of the Bat Survey 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 behavioral burden. It discloses the exact content of the result and implicitly indicates this is a read-only metadata operation by telling the agent to pass answers elsewhere. It could be more explicit about having no side effects, but the behavior is strongly implied.
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 deliver the essential information without redundancy. The content is front-loaded and every sentence contributes meaning, including the cross-reference 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?
Since there is no output schema, the description fully accounts for what the returned data will contain. It names all relevant field metadata and provides the key relationship to submit_enquiry, making the tool self-sufficient for an agent.
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 there is nothing to clarify. The description instead adds meaning to the output fields by naming their attributes and explaining how the field key should be used with submit_enquiry.
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 specifies exactly what the tool exposes: every field of the Bat Survey Cost enquiry with key, label, type, required flag, help text, and allowed options. This clearly separates it from submit_enquiry, since it is about inspecting fields rather than submitting answers.
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 sentence 'Pass answers to submit_enquiry keyed by field key' gives practical usage guidance and connects this tool to the submission sibling. It does not explicitly contrast with enquiry_describe, but the context is clear enough that an agent knows this tool is for field metadata.
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 serves a clearly distinct purpose: enquiry_describe explains the workflow, enquiry_fields provides the schema, and submit_enquiry handles submission. There is no overlap or ambiguity between them.
Two tools use an 'enquiry_' prefix but with different structures (enquiry_describe, enquiry_fields), while submit_enquiry uses a verb-first convention. The naming is readable and thematically consistent, but the conventions are not fully uniform.
Three tools are well-scoped for a focused enquiry submission workflow. Each tool earns its place: describe, schema discovery, and submission.
The server covers the core enquiry lifecycle well: explaining the process, defining fields, and submitting with consent confirmation. There is no status or cancellation capability, but these are not essential for the stated purpose.