Returns business hours and booking options for a Lead Stampede client. If the business has online scheduling, returns a tracked booking URL; otherwise returns phone/email. Works for all client types (service, automotive, ecommerce).
| Name | Required | Description | Default |
|---|---|---|---|
| client_slug | Yes | Unique slug identifying the client. |
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 the full burden. It discloses conditional behavior (returns a tracked booking URL if online scheduling exists, otherwise phone/email) and scope (works for all client types). This goes beyond a basic description, though it omits details like error handling or response format.
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 wasted words. It front-loads the core output, then adds conditional detail and scope, making every sentence earn 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?
Given the tool's low complexity (one parameter, no annotations, no output schema), the description adequately explains the return value and conditional branches. It could mention error scenarios, but for a simple getter, this is sufficient.
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 schema covers the only parameter (client_slug) with a clear description ('Unique slug identifying the client'), so 100% coverage is met. The description adds no additional parameter-specific meaning, so the baseline score of 3 is appropriate.
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 returns business hours and booking options, which is a specific verb+resource combination. It distinguishes itself from sibling tools like get_client or get_reviews by focusing on availability and scheduling, making its 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 description notes it works for all client types (service, automotive, ecommerce), providing useful context for when to use it. However, it does not explicitly mention alternatives or exclusions, though the sibling tools are distinct enough that this is not a major gap.
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 resource or action, but get_client overlaps with get_reviews and get_availability by including reviews and hours in its Agent Card. However, the descriptions clearly differentiate a full profile from specific data points, so confusion is unlikely.
All tools consistently follow a verb_noun snake_case pattern (contact_sales, get_client, list_cities, search_products), making the naming highly predictable and professional.
With 12 tools, the set is well-scoped for a directory and lead-generation platform. Each tool serves a clear purpose, from discovery (list_cities, search_clients) to vertical-specific actions (search_inventory, contact_sales), without unnecessary bloat.
The server covers core directory functions (search, list, get details), availability, reviews, and vertical-specific workflows for automotive and ecommerce. A notable gap is the lack of a generic lead-capture tool for non-automotive clients, but this is a minor limitation given the stated domain.