Skip to main content
Glama

search_services

Find available pet care services in your location by searching Rover's marketplace to connect with sitters and manage bookings.

Instructions

List all available Rover service types in a given location with descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationYesLocation to search for available services

Implementation Reference

  • The handler for the 'search_services' tool that validates the location parameter using SearchServicesSchema, calls browser.searchServices(), and formats the response as a text message listing available services.
    case "search_services": {
      const { location } = SearchServicesSchema.parse(args);
      const services = await browser.searchServices(location);
      const formatted = services
        .map((s) => `• **${s.type.replace(/_/g, " ")}**: ${s.description}`)
        .join("\n");
      return {
        content: [
          {
            type: "text",
            text: `Available Rover services in ${location}:\n\n${formatted}`,
          },
        ],
      };
    }
  • Zod validation schema for search_services input, requiring a non-empty location string.
    const SearchServicesSchema = z.object({
      location: z.string().min(1),
    });
  • src/index.ts:89-103 (registration)
    Tool registration defining 'search_services' with description and JSON Schema inputSchema specifying a required 'location' string parameter.
    {
      name: "search_services",
      description:
        "List all available Rover service types in a given location with descriptions.",
      inputSchema: {
        type: "object",
        properties: {
          location: {
            type: "string",
            description: "Location to search for available services",
          },
        },
        required: ["location"],
      },
    },
  • The searchServices method implementation that navigates to the Rover homepage and returns a hardcoded array of available service types (boarding, house_sitting, drop_in, doggy_day_care, dog_walking) with descriptions.
    async searchServices(location: string): Promise<Array<{ type: string; description: string; availableCount: number }>> {
      const page = this.ensurePage();
      await page.goto(`${this.BASE_URL}/`);
      await page.waitForLoadState("networkidle");
    
      return [
        { type: "boarding", description: "Your dog stays at the sitter's home", availableCount: 0 },
        { type: "house_sitting", description: "Sitter stays in your home", availableCount: 0 },
        { type: "drop_in", description: "Sitter visits your home for 30-60 minutes", availableCount: 0 },
        { type: "doggy_day_care", description: "Your dog spends the day at the sitter's home", availableCount: 0 },
        { type: "dog_walking", description: "Sitter takes your dog for a walk", availableCount: 0 },
      ];
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it's a list operation, implying read-only behavior, but doesn't disclose details like pagination, rate limits, authentication needs, or error handling. For a tool with no annotations, this leaves significant behavioral gaps, scoring low due to insufficient disclosure.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the core action ('List all available Rover service types') and includes key details ('in a given location with descriptions'). There is no wasted text, and it's appropriately sized for the tool's complexity.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally complete. It covers the basic purpose but lacks behavioral details and usage guidelines. Without annotations or output schema, it should provide more context on what the list returns and how to use it effectively, leaving room for improvement.

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%, with the single parameter 'location' fully documented in the schema. The description adds minimal value by implying location-based filtering but doesn't provide additional context like format examples or constraints beyond the schema. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 verb 'List' and the resource 'Rover service types', specifying the scope 'in a given location with descriptions'. It distinguishes from siblings like 'search_sitters' by focusing on service types rather than sitters. However, it doesn't explicitly contrast with other list-like tools such as 'get_bookings' or 'get_favorites', keeping it at 4 instead of 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, exclusions, or compare with sibling tools like 'search_sitters' for finding sitters versus services. The context is implied through the tool name and description but lacks explicit usage instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/markswendsen-code/mcp-rover'

If you have feedback or need assistance with the MCP directory API, please join our Discord server