enquiry_describeRead first. States plainly what submit_enquiry does on Shop Sign 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 full responsibility for behavioral disclosure. It explicitly states that nothing is bought, ordered, or paid, no quote is guaranteed, it is free, and it details exactly what content 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 four short sentences, front-loaded with 'Read first,' and every sentence adds value: purpose, no-purchase clarification, free status, and returned content. No waste or 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 no-input, no-output-schema tool, the description fully covers purpose, behavior, and return content. It also ties the tool to submit_enquiry, giving an agent enough context to invoke it 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 input schema has zero parameters, so there is no parameter semantics to explain. Per the rubric, a zero-parameter tool receives a baseline of 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 Shop Sign Cost' and details what it returns. This clearly differentiates it from sibling tools like submit_enquiry itself and enquiry_fields.
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' clearly signals that this tool should be used before submit_enquiry. It doesn't explicitly mention enquiry_fields or when not to use it, but the intended context 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.
Each tool has a clearly distinct role: one explains the process, one returns the field schema, and one performs the submission. The two-step submit behavior is documented within submit_enquiry itself, so an agent should not confuse it with the informational tools.
The tools share the 'enquiry' root and use snake_case, but the pattern is inconsistent: two are noun-first (`enquiry_describe`, `enquiry_fields`) while the action is verb-first (`submit_enquiry`). This is readable but lacks a single predictable verb_noun convention.
Three tools is appropriate for the narrow enquiry lifecycle: a process explainer, a schema provider, and a submission action. Each tool justifies its existence and there is no bloat.
The surface fully covers the intended workflow: an agent can understand the process, fetch all required fields and options, and submit with the required consent and confirmation token. No additional operations are needed for the stated Shop Sign Cost enquiry purpose.