mcp-wag

get_pet_report

Retrieve a detailed report card for completed pet walks, including photos, walker notes, potty breaks, behavior tags, and route maps by providing the booking ID.

Instructions

Get the report card for a completed walk, including photos, walker notes, potty breaks, behavior tags, and route map. Requires WAG_EMAIL and WAG_PASSWORD.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "booking_id": "<booking_id>"
    },
    "name": "get_pet_report"
  }
}

Input Schema

Name	Required	Description	Default
`booking_id`	Yes	The booking ID of the completed walk to get the report for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 17, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden and effectively discloses key behavioral traits: it's a read operation (implied by 'Get'), requires authentication ('Requires WAG_EMAIL and WAG_PASSWORD'), and specifies the data scope. However, it doesn't mention potential rate limits, error conditions, or response format details.

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 efficiently structured in two sentences: the first clearly states purpose and content, the second specifies authentication requirements. Every element serves a purpose with no wasted words, making it easy to parse quickly.

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 single-parameter read tool with no output schema, the description provides good context: purpose, content details, and authentication requirements. It could be more complete by mentioning response format or error handling, but covers the essential aspects well given the tool's simplicity.

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 'booking_id' well-documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline score of 3 for high schema coverage without additional value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get the report card') and resource ('for a completed walk'), with detailed content listing ('photos, walker notes, potty breaks, behavior tags, and route map'). It distinguishes from siblings like 'get_walk_status' by focusing on post-walk reports rather than current status.

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 implies usage context by specifying 'for a completed walk' and authentication requirements, but doesn't explicitly state when to use this tool versus alternatives like 'get_walk_status' for ongoing walks or 'rate_walker' for feedback. It provides some guidance but lacks explicit comparisons.

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

Deploy Server