enquiry_describeRead first. States plainly what submit_enquiry does on HostingByStack: 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?
Despite having no annotations, the description transparently explains what the tool does not do ('Nothing is bought, ordered or paid; no quote is guaranteed; it is free') and what it returns (who receives details, consent wording, confirmation method). This fully clarifies the tool's behavior and avoids misconceptions.
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 concise and well-structured, consisting of three sentences that each serve a purpose: the directive, the core function, and the clarifications. It avoids unnecessary details and efficiently communicates the essential information.
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?
The description provides sufficient context for an agent to understand when and why to use this tool. It explains the tool's role in relation to submit_enquiry, what it returns, and key limitations, making it complete despite lacking an output schema.
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 is empty (0 parameters), so there are no parameters to describe. The description adds no parameter information, but since 0 parameters have a baseline score of 4, no additional explanation is required.
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 states that the tool 'states plainly what submit_enquiry does on HostingStack', specifying the action (stating), the resource (submit_enquiry), and the context (HostingStack). It also explicitly clarifies what it is not (not a purchase, not a guaranteed quote), making the purpose 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 phrase 'Read first' provides an explicit usage directive, suggesting this tool should be used as a preliminary step. It also describes what the tool returns, giving context on when it is appropriate. However, it does not explicitly compare against sibling tools like 'enquiry_fields', so it lacks direct alternative-based 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.
The dataset_* tools are mostly distinct, but dataset_row and dataset_compare overlap: both retrieve rows by matching a column value, and compare can effectively do row's job with a single value. The enquiry_* tools are clearly separated by behavior, fields, and submission.
Tool names consistently use lowercase snake_case with clear domain prefixes: dataset_* and enquiry_*. However, some names are nouns (dataset_columns, dataset_row, dataset_stats) while others are verbs or adjectives (dataset_compare, dataset_search, dataset_top), so the pattern is not perfectly uniform.
Ten tools is well-scoped for a server covering two clear areas: read-only dataset exploration and enquiry submission. Each tool has a practical role, and the count is comfortably within the ideal range.
The dataset side covers schema, provenance, exact lookup, substring search, comparisons, statistics, and top/bottom rows, which is strong for a read-only dataset server. The enquiry side covers describing the process, listing fields, and submitting with a two-step confirmation, though there is no way to check submission status or cancel an enquiry.