enquiry_describeRead first. States plainly what submit_enquiry does on Forklift Course Finder: 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 and does add meaningful context: no purchase/payment, no guaranteed quote, free, and it returns recipient/consent/confirmation details. However, it never explicitly states that enquiry_describe itself is read-only and has no submission side effects; that must be inferred from the tool name and the 'Read first' instruction.
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 crucial 'Read first' instruction, and each subsequent clause adds a distinct fact. Minor redundancy with the title—not a purchase, no guaranteed quote—prevents a top score.
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, it is reasonably complete: it explains what submit_enquiry does, what it does not do, and what information the description returns. It does not specify output format, but the absence of an output schema and the low complexity make this a minor 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?
There are zero parameters and the schema is trivially complete, so the baseline is 4. The description correctly avoids inventing parameter details where none exist.
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 that this tool states what submit_enquiry does, distinguishing it from the actual submission action. It is somewhat indirect about its own operation—using 'States plainly' and 'Also returns' rather than an explicit 'This tool returns'—but the purpose is recoverable and not misleading.
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' gives an explicit temporal cue: invoke this before submit_enquiry. This is clear usage context, but it does not contrast with enquiry_fields or state when not to use the tool, so it falls short of full alternative guidance.
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: one explains the process, one returns the field schema, and one performs the submission. There is no overlap in purpose.
All names are lowercase snake_case and readable, but the pattern is slightly mixed: two use an enquiry_ prefix while the third leads with the verb submit_. This is a minor deviation from a fully uniform convention.
Three tools is well-scoped for the narrow workflow of describing, inspecting, and submitting an enquiry. Each tool earns its place without redundancy.
The surface fully covers the enquiry workflow: schema discovery, validation preview, and two-step submission with confirmation token. No obvious missing operations for this domain.