enquiry_fieldsEvery field of the Heat Network Check 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?
No annotations are provided, so the description carries the full burden of disclosing side effects. It does not state that this is a read-only operation or whether it requires authentication. While it likely only returns metadata, the description fails to explicitly communicate safety, leaving an agent to assume.
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. The first front-loads the tool's purpose and contents, the second provides a usage hint. No filler or redundancy.
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 simple read-only metadata tool with no output schema and no parameters, the description fully explains what is returned (field attributes) and how to use the result (key for submit_enquiry). Nothing an agent needs to call it correctly is missing.
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 schema is empty, so schema description coverage is trivially 100%. The baseline is 4 for 0 params. The description adds no parameter semantics, but none are needed.
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 Heat Network Check enquiry' with specific attributes (key, label, type, required, help text, options). This distinguishes it from siblings like submit_enquiry (which submits answers) and enquiry_describe (which likely describes the enquiry itself). The verb is implicit but the resource is explicit.
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 a direct usage hint: 'Pass answers to submit_enquiry keyed by field key,' indicating this tool should be used to discover valid field keys before submission. It does not explicitly mention alternatives or when not to use it, but the context is clear.
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.
The checker_* and enquiry_* prefixes cleanly separate the two workflows. Within each group, start, answer, and tree have distinct roles, and describe, fields, and submit are clearly different operations with minimal overlap.
All names use a consistent snake_case format and clear domain prefixes (checker_, enquiry_). However, the pattern is not strictly verb_noun: checker_tree and enquiry_fields are noun-based while others are verb-oriented.
Six tools is a well-scoped set for a site with two focused workflows: a decision-tree checker and an enquiry submission flow. Each tool serves a distinct purpose and none feel redundant or excessive.
The checker tools cover starting, navigating, and inspecting the full decision guide, and the enquiry tools cover explanation, schema discovery, and the full two-step consent submission process. No obvious dead ends or missing lifecycle steps for the stated domain.