Skip to main content
Glama

message_sitter

Send messages to pet sitters on Rover to inquire about services, discuss pet care details, and coordinate bookings through direct communication.

Instructions

Send a message to a sitter on Rover. Requires being logged in.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sitterIdYesSitter's Rover username/ID or profile URL
messageYesMessage text to send to the sitter

Implementation Reference

  • The core handler implementation that executes the message_sitter tool logic. It navigates to a sitter's profile page, clicks the contact/message button, fills in the message textarea, and submits the message.
    async messageSitter(
      sitterId: string,
      message: string
    ): Promise<{ success: boolean; messageId?: string }> {
      if (!this.session.isLoggedIn) {
        throw new Error("You must be logged in to send messages.");
      }
      const page = this.ensurePage();
      const sitterUrl = sitterId.startsWith("http")
        ? sitterId
        : `${this.BASE_URL}/sitters/${sitterId}/`;
      await page.goto(sitterUrl);
      await page.waitForLoadState("networkidle");
    
      const contactBtn = page.locator(
        'button:has-text("Contact"), button:has-text("Message"), a:has-text("Contact")'
      ).first();
      if (await contactBtn.isVisible()) {
        await contactBtn.click();
        await page.waitForLoadState("networkidle");
      }
    
      const textarea = page.locator("textarea").first();
      if (await textarea.isVisible()) {
        await textarea.fill(message);
        const sendBtn = page.locator('button[type="submit"], button:has-text("Send")').first();
        if (await sendBtn.isVisible()) {
          await sendBtn.click();
          await page.waitForLoadState("networkidle");
          return { success: true };
        }
      }
    
      return { success: false };
    }
  • The switch case handler that routes the message_sitter tool call to the browser.messageSitter() function and formats the response.
    case "message_sitter": {
      const { sitterId, message } = MessageSitterSchema.parse(args);
      const result = await browser.messageSitter(sitterId, message);
      return {
        content: [
          {
            type: "text",
            text: result.success
              ? "Message sent successfully!"
              : "Failed to send message. Please try again.",
          },
        ],
      };
    }
  • Zod schema definition that validates the message_sitter tool input parameters: sitterId (non-empty string) and message (non-empty string).
    const MessageSitterSchema = z.object({
      sitterId: z.string().min(1),
      message: z.string().min(1),
    });
  • src/index.ts:150-165 (registration)
    Tool registration defining the message_sitter tool with its name, description, and JSON Schema input specification for the MCP protocol.
    {
      name: "message_sitter",
      description: "Send a message to a sitter on Rover. Requires being logged in.",
      inputSchema: {
        type: "object",
        properties: {
          sitterId: {
            type: "string",
            description: "Sitter's Rover username/ID or profile URL",
          },
          message: {
            type: "string",
            description: "Message text to send to the sitter",
          },
        },
        required: ["sitterId", "message"],
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the login requirement, which is a useful behavioral constraint, but fails to disclose other critical traits like whether this is a read/write operation, potential rate limits, confirmation of message delivery, or error conditions. This leaves significant gaps for a tool that likely performs a write action.

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 extremely concise with just two sentences, front-loading the core purpose and following with a key prerequisite. Every word earns its place with no redundancy or fluff, making it efficient and well-structured.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is insufficient for a tool that likely performs a write operation (sending a message). It misses details like response format, error handling, side effects, or how it differs from sibling tools, leaving the agent with incomplete context for safe and effective use.

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 both parameters. The description adds no additional parameter information beyond what's in the schema, such as format examples or constraints. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('Send a message') and target ('to a sitter on Rover'), making the purpose understandable. However, it doesn't differentiate this tool from sibling tools like 'get_messages' or 'request_booking' that might also involve messaging, which prevents a perfect score.

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?

The description provides one explicit usage condition ('Requires being logged in'), which is helpful context. However, it doesn't specify when to use this tool versus alternatives like 'request_booking' (which might include messaging) or 'get_messages', leaving usage guidance incomplete.

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