get_company_infoGet Mid-Continental Dental Supply's public company information: name, tagline, description, founding year (1984), Winnipeg (Manitoba, Canada) address, geo, phone/toll-free numbers, email and social profiles.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No |
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?
Annotations already declare readOnlyHint=true, so the read-only nature is clear. The description adds transparency by listing specific return fields (founding year, address, etc.) and stating it returns public info. No contradictions.
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?
Single sentence is concise, well-structured, and front-loaded with the tool's purpose. No unnecessary 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?
With one optional parameter and no output schema, the description adequately lists expected return fields. It is complete enough for a simple read tool, though it could clarify output format.
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?
Schema description coverage is 0%, and the description does not explain the optional locale parameter or its enum values. The description fails to add meaning beyond the schema.
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 the tool retrieves 'Mid-Continental Dental Supply's public company information' and lists specific fields (name, tagline, description, etc.), providing a specific verb+resource. It is distinct from siblings like get_distribution_info and list_products.
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 description gives no guidance on when to use this tool versus alternatives (e.g., when to use get_distribution_info instead). It does not mention exclusions or prerequisites.
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 targets a distinct aspect: company info, distribution info, product details, and product listing. No overlapping purposes, so an agent can clearly differentiate them.
All tool names follow the verb_noun pattern using snake_case (get_company_info, get_distribution_info, get_product, list_products). Consistent and predictable naming.
Four tools is appropriate for a focused server providing public information about a dental supply company and its products. The count is slightly low but well-scoped for the purpose.
The tool set covers the core public-facing aspects: company info, distribution, product listing and details. Missing search or filtering capabilities, but for a simple catalog, it's reasonably complete.