getServiceCatalogDevuelve los tipos de servicio que ofrece Cooper (paseos, adiestramiento, guardería, internación) con sus planes y rangos de precio en ARS. Invocar siempre antes de mencionar precios, aun cuando sean orientativos. El precio definitivo de cada servicio lo determina el cuidador asignado dentro del rango publicado, y el usuario lo confirma al crear la orden.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the transparency burden. It adds valuable behavioral context: prices are ranges, the final price is set by the assigned caregiver, and the user confirms it at order creation. This prevents the agent from misrepresenting prices. It doesn't explicitly mention read-only status, but 'Devuelve' implies a read operation.
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 long, front-loaded with the main purpose, followed by actionable usage guidance. Every sentence contributes essential information with no redundancy or filler.
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 zero-parameter tool with no output schema and no annotations, the description is remarkably complete. It states what is returned, when to use it (always before mentioning prices), and the key caveat about final pricing. The agent has all necessary context to invoke this tool correctly.
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 0 parameters, so the baseline is 4. The description doesn't need to explain parameters, and the schema fully covers the (empty) parameter set. The description adds context about the return content, which is not parameter-related but still useful.
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 ('Devuelve') and resource ('tipos de servicio que ofrece Cooper') with concrete examples (paseos, adiestramiento, guardería, internación). This clearly distinguishes it from sibling tools like getBreeds, making its purpose unmistakable.
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 explicitly instructs to 'Invocar siempre antes de mencionar precios, aun cuando sean orientativos', providing a clear when-to-use rule. It also explains the pricing determination flow, implying this tool is for ranges only and not final quotes.
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: coverage checks, lead capture, order creation, breed catalog, chats, orders, pets, service catalog, shifts, and messaging. No two tools could be confused for the same purpose.
All tool names follow a consistent camelCase verb_noun pattern (checkCoverage, createLead, createOrder, getBreeds, getChatMessages, etc.). The pattern is predictable and uniform across the entire set.
12 tools is well-scoped for a pet service booking assistant. Each tool covers a clear need without being excessive or sparse.
Core workflows are covered: coverage, ordering, pets, chat, and service catalog. Minor gaps exist like no update/cancel order or add/edit pet, but agents can work around these as the primary booking flow is complete.