enquiry_describeRead first. States plainly what submit_enquiry does on Texas Foundation Repair 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 and does so excellently. It explicitly states that nothing is bought, ordered, or paid, that no quote is guaranteed, that the service is free, and what information is returned.
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 critical guidance 'Read first.' Every sentence earns its place: it explains the tool's purpose, explicitly negates purchase/payment/guarantee assumptions, and summarizes the returned content without 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 zero-parameter descriptive tool with no output schema and no annotations, the description is fully self-sufficient. It tells the agent what the tool does, what it doesn't do, and what information will be returned, leaving no critical gap.
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 fully covers the parameter space by definition. The description adds meaningful context about what the tool returns and its non-action nature, exceeding the baseline expectation for a parameterless tool.
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 tool as an explanatory companion to submit_enquiry, stating that it 'describes what submit_enquiry does' rather than performing the submission. It is immediately distinguishable from submit_enquiry (which actually starts an enquiry) and enquiry_fields (which likely handles field details).
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?
'Read first' explicitly signals that this tool should be used before interacting with submit_enquiry, giving the agent clear context for when to call it. It does not spell out exclusions or compare against enquiry_fields, but the intended usage is evident.
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 provides the plain-language overview, enquiry_fields provides the exact field schema, and submit_enquiry handles the actual two-step submission. There is no functional overlap between them.
The names are readable and share the 'enquiry' concept, but the pattern is mixed: enquiry_describe and enquiry_fields use an enquiry_ prefix, while submit_enquiry uses a verb-first convention. This makes the naming slightly inconsistent even though it is not confusing.
Three tools is a well-scoped set for this simple enquiry workflow: orientation, field definitions, and submission. Each tool earns its place and there is no redundancy.
For the stated purpose of submitting an enquiry, the set covers everything needed: understanding the process, retrieving the required fields, and performing the validated two-step submission with consent. There are no obvious gaps or dead ends.