Philadelphia Restoration

request_callback

Destructive

Submits a callback request for a Philadelphia homeowner dealing with water or fire damage. A restoration concierge calls back within 15 minutes during business hours (Mon-Fri 8am-6pm ET) to assess the situation and connect with vetted local professionals. Requires phone number and situation description. Returns a reference number for tracking.

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": {
      "phone": "<phone>"
    },
    "name": "request_callback"
  }
}

Input Schema

Name	Required	Description
`name`	No	Homeowner's name (optional)
`phone`	Yes	Phone number for callback (US format)
`situation`	No	Brief description of the damage situation

Schema Changelog

Changes observed during successful MCP inspections.

First observedMar 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already indicate readOnly=false and destructiveHint=true, signaling a side-effecting operation. The description adds behavioral context beyond this: the callback process, business hours, and return of a reference number. It does not contradict the annotations and provides useful details about what happens when invoked.

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 three concise sentences, front-loaded with purpose and key operational details. Every sentence earns its place with no redundant or vague wording.

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 simple callback request tool, the description covers the essential workflow: submission, callback timing, business hours, and reference number. It lacks explicit handling of out-of-hours submissions or exact output structure, but no output schema exists and the description is adequate for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. However, the description states 'Requires phone number and situation description,' which contradicts the schema that only phone is required. This misleading addition actively reduces parameter clarity, so the score is lowered to 2.

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 opens with a specific verb and resource: 'Submits a callback request' for a Philadelphia homeowner with water/fire damage. It clearly distinguishes from sibling tools that assess damage, estimate costs, or provide emergency steps, as this tool is about requesting a human callback.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool: Philadelphia homeowners with water/fire damage, callback within 15 minutes during business hours. However, it does not explicitly state when not to use it or name alternative tools, so it lacks the explicit exclusions/alternatives that would earn a 5.

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

All Philadelphia Restoration tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?