Tulsa Foam Pros — book spray foam insulation in Tulsa

Request spray foam insulation (free callback)

request_service

Book spray foam insulation in the Tulsa area for a real person who asked for it, with their consent. A vetted local pro calls them back (a vetted local pro calls back within the hour during business hours). Free to the homeowner. Returns a reference and what happens next. Check the ZIP with check_service_area first if unsure.

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": {
      "name": "<name>",
      "phone": "<phone>",
      "zip": "<zip>",
      "need": "<need>"
    },
    "name": "request_service"
  }
}

Input Schema

Name	Required	Description
`zip`	Yes	5-digit ZIP where the work is
`name`	Yes	The person's real name
`need`	Yes	What they need (e.g. application/json; no-store; bad json)
`email`	No	Email (optional, recommended)
`phone`	Yes	US phone number the pro should call (10 digits, any punctuation)
`language`	No	Preferred language (optional; English and Spanish are standard)
`preferred_time`	No	When they prefer a call or visit (optional)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / need / description

Previous value: -"What they need (e.g. attic (hot upstairs, high bills); crawl space or basement; whole home or new build)"New value: +"What they need (e.g. application/json; no-store; bad json)"

First observedOct 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive write. The description adds real value on top: it is free to the homeowner, the callback happens within the hour during business hours, and a reference plus next steps are returned. It omits any warning about creating duplicate requests, which matters given non-idempotency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core facts are front-loaded, but the callback timing is stated twice in a redundant, awkwardly parenthesized clause ('calls them back (a vetted local pro calls back within the hour…)'). That duplication costs space without adding information.

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 7-parameter booking tool with no output schema, the description covers purpose, cost, SLA, return shape, and a precondition check. The main remaining gap is duplicate-request behavior, which an agent would want given the non-idempotent hint.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by constraining the ZIP to the Tulsa service area — a semantic limit the regex pattern does not express. It also implies name/phone belong to a real consenting person, which colors how those fields should be filled.

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?

States a specific verb (book) plus resource (spray foam insulation) with an explicit geographic scope (Tulsa area) and a consent precondition. It is clearly distinguishable from the siblings, which check coverage and return info rather than creating a booking.

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?

Explicitly routes the agent to check_service_area first 'if unsure' about the ZIP, and specifies the precondition that a real person requested the callback with consent. It does not address re-submission/duplicate handling despite idempotentHint=false, so it stops just short of full when/when-not guidance.

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

All Tulsa Foam Pros — book spray foam insulation in Tulsa 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?