Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rover_trainer_profile

Retrieve a Rover dog trainer's profile by slug, including name, photo, headline, experience, availability, methodology, rating, reviews, repeat clients, years training, skill tags, and credentials.

Instructions

Get Rover dog trainer profile. Returns a Rover dog trainer profile: name, photo, headline, experience and availability details, training methodology, rating, review count, repeat-client count, years of training, skill/behavior tags, and education credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesRover trainer profile slug, the trailing path segment of a trainer search result's profile_url field

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?

No annotations are provided, so the description carries the full burden. It discloses the shape of the response (rating, review count, credentials, etc.), which usefully signals a read-only lookup, but says nothing about auth requirements, rate limits, or error behavior for an unknown slug.

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, front-loaded with the action before the field enumeration. The long field list is somewhat listy but earns its place given there is no output schema.

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?

With no output schema and no annotations, enumerating the returned fields is exactly the compensating detail needed for a simple one-parameter read tool. Only the missing usage/routing context keeps it from being fully complete.

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% and the slug parameter is well documented there (trailing path segment of profile_url). The description adds no meaning beyond the schema, so the baseline 3 applies.

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 and resource ('Get Rover dog trainer profile') and enumerates the returned fields, so the agent knows exactly what entity this retrieves. It does not explicitly name or contrast with the sibling rover_trainer_search, but the detail-vs-search distinction is inferable from the name and resource.

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 when-to-use guidance, no prerequisite stating that a slug must first come from a search, and no mention of alternatives such as rover_trainer_search or rover_sitter_profile. The description is purely descriptive of what comes back.

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