Get one Servana vendor's public profile: name, description, services + pricing, verification status, rating, and page URL.
| Name | Required | Description | Default |
|---|---|---|---|
| vendor_slug | Yes | The vendor's slug from search_vendors results or a servana.ai vendor URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds that this is a public profile fetch and lists the fields an agent can expect, though it does not describe error behavior for a missing or invalid slug.
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 one tight, front-loaded sentence that names the action, subject, and expected contents without redundant words. It carries exactly the information an agent needs at a glance.
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?
Even without an output schema, the description explicitly lists the return contents: name, description, services and pricing, verification status, rating, and page URL. Combined with the detailed parameter schema and safety annotations, this is complete for a simple read-only lookup tool.
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 coverage is 100%: the single parameter is required and clearly documented as the vendor slug from search_vendors or a URL. The tool description adds no additional parameter 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 uses a specific verb ('Get'), names the exact resource ('one Servana vendor's public profile'), and enumerates the returned fields. The singular scoping distinguishes it from search-oriented siblings like search_vendors and search_services.
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 parameter description clarifies that vendor_slug comes from search_vendors results or a servana.ai URL, implying this tool is used after identifying a specific vendor. It does not explicitly contrast it with search_vendors or other alternatives, 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 targets a distinct action: estimating pricing, fetching a single vendor, mapping free text to service categories, searching vendors, and messaging vendors. Even though search_vendors and get_vendor both involve vendor data, one returns lists based on criteria and the other retrieves a specific profile, so there is no ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case: estimate_service_request, get_vendor, search_services, search_vendors, send_message_to_vendor. The verbs (estimate, get, search, send) are clear and match the action.
Five tools is well-scoped for a service discovery and booking directory. Each tool serves a necessary step in the user workflow without redundancy, and the count is neither too sparse nor overloaded.
The tool surface covers the full lifecycle for a user: discovering service categories, finding vendors, getting price estimates, viewing vendor details, and contacting vendors. There are no obvious missing operations that would prevent an agent from accomplishing the server's intended purpose.
