enquiry_describeRead first. States plainly what submit_enquiry does on Forklift Servicing 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 provided, the description carries the full burden of explaining behavior. It clearly states that nothing is bought, ordered, or paid, that no quote is guaranteed, that the service is free, and what information is returned. This gives an agent an accurate model of the tool's non-transactional, informational 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 three concise sentences with no filler. It front-loads the most important guidance ('Read first') and then delivers key behavioral facts and return-value details in a compact, well-ordered way.
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 states what the tool does, what it does not do, and exactly what it returns (recipients of details, consent wording, confirmation method). An agent has enough to use and interpret the tool correctly.
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 no schema information needing elaboration. The description appropriately focuses on behavior and return content rather than inventing parameter details.
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 title and description clearly state that this tool explains what submit_enquiry does, rather than being a purchase or guaranteed quote. It names the specific resource (Forklift Servicing Cost enquiry) and the sibling tool (submit_enquiry), so an agent can distinguish it from the actual submission action.
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' is explicit guidance to consult this tool before taking action, and the description frames it as a prerequisite for understanding submit_enquiry. It does not explicitly contrast with enquiry_fields, but the intended sequence and informational purpose are 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.
Each tool has a distinct role: describe explains the workflow, fields provides the schema, submit sends the enquiry. There is no overlap between the three.
All names use snake_case and share the 'enquiry' theme, but the pattern is inconsistent: enquiry_describe is noun-verb, enquiry_fields is noun-noun, and submit_enquiry is verb-noun. Readable, but not a uniform convention.
Three tools are exactly right for this narrow enquiry workflow: one to understand the process, one to get the schema, and one to submit. No redundant tools.
The tool set fully covers the enquiry lifecycle described: discover what the tool does, fetch the required fields, validate and submit with consent and confirmation. There are no obvious missing operations for the stated purpose.