enquiry_fieldsEvery field of the The Water Hub 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 for behavioral disclosure. It implies a read-only metadata lookup by listing returned properties, but it does not explicitly state that no side effects occur, that no submission is made, or describe any other runtime behavior.
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 compact and front-loads the core content: what fields are returned and how to use them. It loses a point for the typo 'the The' and for slightly awkward phrasing, but it is otherwise efficient.
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 zero parameters and no output schema, the description adequately explains the return content and the downstream usage. It is not fully complete because it does not describe the output format or explicitly disambiguate from enquiry_describe, but nothing essential is missing for a simple metadata lookup.
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 schema is trivially complete. The description adds value by explaining that the returned field keys are meant to be used as keys when calling 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 clearly identifies what the tool returns: every field of the Water Hub enquiry, including key, label, type, required status, help text, and allowed options. It connects to submit_enquiry, but it does not explicitly distinguish itself from the 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?
The description gives clear usage context: retrieve the field definitions, then pass answers to submit_enquiry keyed by field key. It does not state exclusions or when not to use it, but the intended workflow is obvious.
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 targets a distinct operation on the dataset or enquiry. dataset_search, dataset_row, dataset_compare, and dataset_top have clear differences in matching logic and output. Enquiry tools are clearly separate. No two tools appear to do the same thing.
All dataset tools follow a dataset_* pattern, and enquiry tools follow enquiry_* except submit_enquiry which inverts the order. This is a minor deviation but the overall naming is predictable and clear.
10 tools is well-scoped for the domain, covering both data querying and enquiry submission without bloat.
The dataset query surface covers schema, metadata, row lookup, search, stats, and top/bottom. Enquiry covers description, fields, and submission. Minor gaps like a 'list all rows' or enquiry status check exist but are not critical.