enquiry_describeRead first. States plainly what submit_enquiry does on Arizona Roof Replacement Cost: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
| 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 full burden of behavioral disclosure. It clearly says nothing is bought, ordered, paid, or guaranteed, and it is free. It also states what the tool returns: who receives the details, the consent wording, and how the person confirms. This makes the tool's behavior transparent for an informational, zero-parameter tool.
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-loaded with the key usage instruction 'Read first.' Every sentence adds relevant information: what the tool describes, what it is not, and what it returns. There is no filler or repetition of schema content.
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 informational tool with no output schema, the description is complete. It says what the output covers — submit_enquiry's behavior, recipients, consent wording, and confirmation method — and gives enough context for the agent to know why it exists and when to read it.
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 the baseline of 4 applies. There are no parameter semantics for the description to clarify, and the description does not need to compensate for any schema gap.
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 states the tool's job directly: it explains what submit_enquiry does on Arizona Roof Replacement Cost. It distinguishes this 'describe' tool from the action tool submit_enquiry and makes plain that no purchase or guaranteed quote is involved. A reading agent can confidently tell this apart from its siblings.
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 opening 'Read first' is an explicit usage signal: this tool should be used before interacting with submit_enquiry, because it explains the enquiry process and consent details. It gives clear context for when to use it, though it does not explicitly name alternatives or state when not to use it.
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 covers a distinct concern: enquiry_describe explains the process, enquiry_fields provides the exact schema, and submit_enquiry performs the actual submission. There is no functional overlap between reading instructions, reading fields, and acting.
All names are snake_case and clearly tied to 'enquiry', but the word order is mixed: enquiry_describe and enquiry_fields are noun-first, while submit_enquiry is verb-first. This is readable but not a consistent verb_noun pattern.
Three tools is a well-scoped size for a single enquiry submission workflow. Each tool has a necessary role and none feel redundant.
The set covers the full required flow: understand the process, inspect the field schema, submit with consent and confirmation. No obvious dead-ends remain for the stated purpose of submitting an Arizona roof replacement enquiry.