Skip to main content
Glama

Request a service callback

request_service

Ask AtlantFlow to call a customer back about service. ONLY call when the person explicitly asked to be contacted and gave their name, phone and ZIP. Side effect: creates a lead in AtlantFlow's Housecall Pro CRM and notifies the office; nothing is deleted or overwritten. Not idempotent but protected: repeated identical requests are de-duplicated and rate-limited, so do not retry on success. This is a callback request, not a confirmed appointment. For emergencies the person should call (561) 510-9414 directly.

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>",
      "issue": "<issue>",
      "urgency": "<urgency>"
    },
    "name": "request_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit ZIP code of the property.
nameYesCustomer's name.
emailNoCustomer's email (optional).
issueYesWhat is wrong or what is needed, e.g. 'AC blowing warm air', 'quote for new system'. 3-600 characters.
phoneYesCustomer's US phone number, e.g. '561-555-0142'.
urgencyYesHow soon service is needed.
websiteNoAnti-spam honeypot. Leave EMPTY. Never fill this field.
preferred_timeNoPreferred callback or visit time, free text (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The annotations already declare non-readonly, open-world, non-idempotent, and non-destructive behavior. The description adds valuable specifics beyond that: it creates a lead in Housecall Pro CRM, notifies the office, deletes or overwrites nothing, de-duplicates repeated identical requests, applies rate limiting, and should not be retried on success.

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 front-loaded with the purpose and the critical usage restriction, then layers in side effects, idempotency, and the emergency alternative. Every sentence carries operational value, and the emergency phone number is appropriately placed at the end.

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 mutating, externally visible request tool with no output schema, the description covers the important behavioral context: consent requirements, CRM lead creation, office notification, non-idempotency, de-duplication, and emergency routing. The remaining gap is that it does not say what response the agent should expect on success, such as a confirmation or lead reference.

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 already documents all eight parameters. The description reinforces that name, phone, and ZIP are consent-related required fields, but it adds no syntax or additional meaning for issue, urgency, preferred_time, email, or the honeypot field beyond what the schema already provides.

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 states a specific verb and resource: asking AtlantFlow to call a customer back about service. It clearly distinguishes this callback request from a confirmed appointment and from emergency calls, so an agent can identify the tool without opening the schema.

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?

It gives a strong, explicit precondition: ONLY call when the person explicitly asked to be contacted and provided name, phone, and ZIP. It also routes emergencies to a direct phone call and clarifies that this is not an appointment, though it does not explicitly name which sibling tool to use for booking or service-area checks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources