enquiry_describeRead first. States plainly what submit_enquiry does on What Can I Drive: 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 full responsibility for behavioral disclosure. It clearly states that the tool describes a submission process rather than performing it, that nothing is bought, ordered, or paid, that no quote is guaranteed, and that it is free. It also discloses what the description returns: recipient details, consent wording, and confirmation method. This is thorough for an informational 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 two sentences with no filler. 'Read first' is a succinct, front-loaded directive. Every clause adds value: it explains the tool's purpose, what submit_enquiry does, what it does not do, and what information the description provides.
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 informational tool with no parameters and no output schema, the description is complete. It explains the tool's role, the nature of the submission process, limitations, costs, and the content of the returned description. An agent has everything needed to decide whether and when to call 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, so parameter documentation is not needed. The schema coverage is vacuously 100%, and the description adds no parameter-related content, which is appropriate. Baseline for zero-parameter tools is 4.
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 explicitly states the tool's function: it 'States plainly what submit_enquiry does' on What Can I Drive. The title and description clarify that it is an informational description, not the actual submission action, thus clearly distinguishing it from submit_enquiry. The purpose is specific and unambiguous.
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' explicitly instructs the agent to use this tool before submitting an enquiry, establishing clear usage context. It also contrasts the enquiry with a purchase or guaranteed quote, helping the agent understand when this tool's information is relevant. It does not explicitly name alternative tools, but the positioning 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 tool set cleanly separates two distinct workflows: the checker tools for navigating a decision guide and the enquiry tools for submitting a form. Within each group, every tool has a clearly different role—start, answer, tree, describe, fields, submit—so an agent is unlikely to confuse them.
Most tools follow a resource-prefix pattern such as checker_start, checker_answer, checker_tree, enquiry_describe, and enquiry_fields. The exception is submit_enquiry, which uses verb_noun form instead of the enquiry_ prefix, and checker_start/answer/tree mix verb and noun suffixes, creating a minor inconsistency.
Six tools is well-scoped for a site with two distinct user-facing features. Each tool serves a necessary step in its workflow, and there are no redundant utilities or excessive entries.
The checker workflow is fully covered: start, per-step answers, and full tree access for validation. The enquiry workflow is also complete with explanation, field schema, and a two-step submission flow that includes consent and confirmation handling.