get_business_infoReturns approved public business information for Cosmopolitan Company: name, website, phone, email, address, description, and service areas across the Oklahoma City metro.
| 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?
No annotations are present, so the description carries the full burden. It usefully discloses that the data is 'approved public' and enumerates the returned fields, signaling a read-only lookup. It does not cover auth expectations, data freshness, or error behavior, but for a zero-parameter getter that is an acceptable baseline.
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?
A single compact sentence with no filler, front-loaded with the verb and resource, and the field list is scannable and easy to parse. Every part of the description earns its place.
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-parameter, no-output-schema business-info tool, the description fully covers what the agent will receive: name, website, phone, email, address, description, and service areas. No additional context is necessary for correct selection and invocation.
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 and an empty schema, so the baseline is 4. The description adds no parameter semantics because none exist; it instead helpfuly lists the fields the agent can expect in the response.
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 starts with the specific verb 'Returns' and identifies the exact resource: approved public business information for Cosmopolitan Company, followed by an explicit field list. This clearly differentiates it from the readiness-planner sibling tools.
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 use case is implied: call this tool when you need Cosmopolitan Company's public business details. However, the description does not explicitly state when to use it over alternatives or when to avoid it; the gap is minor because there are no parameters and the siblings are unrelated.
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: retrieving company information, retrieving planner metadata, and running the readiness assessment. There is no overlap or ambiguity between them.
The naming follows a consistent snake_case pattern with clear verb prefixes: get_ for informational retrieval and run_ for executing the assessment. This makes the tool set predictable and easy for an agent to navigate.
Three tools is well-scoped for this specialized readiness planner server. Each tool serves a distinct and necessary function without redundancy or bloat.
The server covers the full intended workflow: learning about the company, understanding the planner, and running the planner to get results. No obvious gaps exist for the stated purpose of producing a readiness brief.