Fast Fibre: fiber internet check

Request a call from a specialist

request_callback

Idempotent

Ask Fast Fibre to call the person about fiber internet at their address. Only when the person asked you to, with their own name and mobile number — never guess them. Before calling this tool, tell the person and get their yes to: "The person asked their AI assistant to request a call from Fast Fibre about fiber internet at this address, and agreed that Fast Fibre may call them at this number to confirm the request." Then set user_confirmed to true. A specialist calls usually the same day to confirm the request; nothing is ordered until the person confirms on that call. Relay the message in the result to the person, with the confirm link if there is one.

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>",
      "street": "<street>",
      "zip": "<zip>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "request_callback"
  }
}

Input Schema

Name	Required	Description
`zip`	Yes	5-digit ZIP code
`name`	Yes	The person's name, as they gave it
`plan`	No	"500" = 500 Mbps, "1g" = 1 Gig, "2g" = 2 Gig, "help" = not sure yet (default)
`unit`	No	Apartment or unit, if any
`agent`	No	Your name as an assistant, e.g. "ChatGPT" or "Claude"
`phone`	Yes	The person's 10-digit US mobile number, as they gave it. Never guess it.
`extras`	No	"wifi" = whole-home Wi-Fi, "phone" = home phone
`street`	Yes	House number and street, e.g. "511 Azalea St"
`best_time`	No	When the person prefers a call
`situation`	No	"xfinity" = switching from Xfinity, "other" = from another provider, "moving" = moving in / no internet
`user_confirmed`	Yes	true only after the person asked you to request the call and agreed to this: The person asked their AI assistant to request a call from Fast Fibre about fiber internet at this address, and agreed that Fast Fibre may call them at this number to confirm the request.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare a non-readonly, idempotent, open-world action, and the description adds substantial context beyond them: the mandatory consent gate, that a specialist calls the same day, that nothing is ordered until the person confirms on that call, and that the result message (including any confirm link) must be relayed back.

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

Conciseness4/5

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

Purpose and the core constraint are front-loaded and every sentence carries operational weight (consent, next step, result relay). However, the consent sentence largely restates the user_confirmed schema text verbatim, adding some redundancy and length.

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?

With no output schema, the description still covers prerequisites, consent, what happens next, and how to handle the result, which is thorough. Its one gap is that it never ties into the check_fiber_availability sibling or states whether availability should be verified before requesting a callback.

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; the description still adds meaning by constraining name and phone ('as they gave it', 'never guess it') and by explaining that user_confirmed may only be true after the person requested the call and agreed to the quoted consent text.

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 opening sentence states a specific verb and resource: asking Fast Fibre to call a person about fiber internet at their address. It is clearly distinct from check_fiber_availability in practice, but the description never names that sibling, so an agent must infer the relationship between the two tools.

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

Usage Guidelines5/5

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

It gives explicit when-to-use and when-not-to-use conditions: only when the person asked for the call, with their own name and mobile number, never guessing them. It also dictates the exact consent step and the required user_confirmed flag before calling.

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

All Fast Fibre: fiber internet check 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?