Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rover_trainer_search

Search Rover dog trainer listings by location to compare trainer profiles, ratings, experience, pricing, and training methods.

Instructions

Search Rover dog trainers. Searches Rover's public dog trainer listings by location, returning trainer summaries (name, profile image, headline, experience details, rating, review count, repeat-client count, years of experience, city/state/zip, starting price, training methodology, and skill/behavior tags).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationYesFree-text address, city, or zip code, e.g. \

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It discloses that the data is public and lists the return fields in detail, but omits pagination, result limits, sorting, and authentication requirements.

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 with the purpose front-loaded. The long list of return fields is verbose but justified because no output schema exists. It could be slightly more readable if the list were structured.

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 simple one-parameter search with no annotations and no output schema, the description covers purpose and return fields in useful detail. However, it lacks guidance on choosing search vs profile and omits operational details like pagination or result limits.

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% for the single location parameter. The description only repeats 'by location' and adds no extra syntax, format, or constraint beyond what the schema already provides, so baseline 3 is 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?

States a specific verb ('Search') and resource ('Rover dog trainers') with scope ('public dog trainer listings by location'). It distinguishes itself from sitter siblings by noun, but does not explicitly differentiate from rover_trainer_profile or rover_sitter_search.

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 when-to-use guidance, prerequisites, or alternatives are given. The phrase 'by location' only implies that a location input is needed, but provides no context on when to choose this search over the sibling rover_trainer_profile.

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