Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rover_sitter_search

Search Rover sitters and walkers by location and service type. Filter by pet type, price, and Star Sitter status; get profiles with ratings and reviews.

Instructions

Search Rover sitters and walkers. Searches Rover's public sitter/walker listings by location and service type, returning sitter summaries (name, profile image, rating, review count, repeat-client count, years of experience, neighborhood/city/state, starting price, Star Sitter status, and a short bio).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based result page. Defaults to 1.
locationYesFree-text address, city, or zip code, e.g. \
pet_typeNoFilter by pet species. One of: `dog`, `cat`.
max_priceNoMaximum starting rate in whole dollars.
min_priceNoMinimum starting rate in whole dollars.
service_typeYesService category to search. One of: `overnight-boarding`, `overnight-traveling`, `drop-in`, `doggy-day-care`, `dog-walking`.
star_sitter_onlyNoRestrict results to Rover's \

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose two useful traits: that the listings are 'public' (implying no auth/private data) and an explicit inventory of returned fields. It does not describe pagination behavior, result caps, or ordering despite a 'page' parameter existing, so the behavioral picture is only partial.

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?

The purpose is front-loaded in the very first clause, and the second sentence earns its length by enumerating return fields that are not documented anywhere else (no output schema). The parenthetical list is long but serves a real gap rather than restating structured data.

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

Completeness4/5

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

For a 7-parameter search with no output schema and no annotations, the description does the essential work: it states the source, the filtering dimensions, and the shape of each result. The remaining gap is operational detail (paging through results, sort order, result limits), which is a moderate omission rather than a blocking one.

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 already documents all seven parameters and their semantics. The description reinforces the two most important filters (location, service type) but adds no format, default, or interaction detail beyond what the schema provides, making the baseline 3 appropriate.

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 gives a specific verb and resource ('Search Rover sitters and walkers') and narrows it further with 'searches Rover's public sitter/walker listings by location and service type', which cleanly separates it from rover_trainer_search. It stops short of naming the sibling rover_sitter_profile that an agent would use for follow-up detail, so it is clear but not fully sibling-routing.

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

Usage Guidelines3/5

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

Usage is implied: 'searches ... by location and service type' tells an agent this is the entry point for finding sitters in a given area. However, there is no explicit when-to-use, no when-not-to-use, and no pointer to rover_sitter_profile for per-sitter detail, so the routing guidance is left to inference.

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

Deploy Server

Other Tools