PetSmart MCP Server

schedule_grooming

Book grooming appointments for pets at PetSmart, including services like bath & brush, haircuts, nail trims, and full grooming packages.

Instructions

Book a grooming appointment for your pet at PetSmart. Services include bath & brush, haircut, nail trim, and full grooming packages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pet_name": "<pet_name>",
      "pet_type": "<pet_type>",
      "breed": "<breed>",
      "service_type": "<service_type>",
      "preferred_date": "<preferred_date>"
    },
    "name": "schedule_grooming"
  }
}

Input Schema

Name	Required	Description
`pet_name`	Yes	Name of your pet
`pet_type`	Yes	Type of pet (e.g., 'dog', 'cat')
`breed`	Yes	Breed of your pet
`service_type`	Yes	Grooming service (e.g., 'bath & brush', 'haircut', 'nail trim', 'full groom', 'puppy bath')
`preferred_date`	Yes	Preferred appointment date (YYYY-MM-DD format)
`preferred_time`	No	Preferred appointment time (e.g., 'morning', 'afternoon', '10:00 AM')
`store_id`	No	PetSmart store ID (optional, will use zip_code if not provided)
`zip_code`	No	ZIP code to find nearby stores

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 15, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only states what the tool does, not behavioral traits like whether it confirms bookings, handles conflicts, requires authentication, or has rate limits. It mentions optional parameters but doesn't explain their impact on behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences are front-loaded with the core purpose and service examples, with no redundant information. It's efficient, though slightly more detail on behavioral aspects could improve completeness without sacrificing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 8 parameters, no annotations, and no output schema, the description is adequate but incomplete. It covers the purpose and services, but lacks behavioral context, usage guidelines, and output expectations, leaving gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents parameters. The description adds minimal value by listing service examples, but doesn't provide additional semantics beyond what's in the schema, such as format details or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Book a grooming appointment') and resource ('for your pet at PetSmart'), with specific service examples. It distinguishes from siblings like 'schedule_training' by focusing on grooming, though it doesn't explicitly contrast with other scheduling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like 'find_store' for location lookup or 'schedule_training' for other services. The description implies usage for grooming appointments but lacks context about prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server