playbooks

home / skills / contextware / skills / service-qualification-check

service-qualification-check skill

/skills/service-qualification-check

This skill checks if a requested service is available at a given address using Telepath MCP servers and service specifications.

npx playbooks add skill contextware/skills --skill service-qualification-check

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
2.2 KB
---
name: service-qualification-check
description: Checks if a specific service is available at a given address.
metadata:
  createdAt: '2026-02-07T19:36:51.399Z'
allowed-tools:
  - telepath_service_qualification
  - telepath_list_service_specifications
mcp-servers:
  - telepath
---
---name: service-qualification-check
description: Checks if a specific service is available at a given address.
mcp-servers: ["telepath"]
allowed-tools: ["telepath_service_qualification", "telepath_list_service_specifications"]
---

## Skill Description

This skill checks if a specific service is available at a given address using the Telepath MCP server.

## Workflow

1.  The user provides an address (street number, street name, city) and the desired service type.  For example: "Can you check if fiber is available at 123 Main Street, Anytown?".
2.  The skill uses the `telepath_list_service_specifications` tool to find the service specification ID that matches the provided service type.
    *   If no matching service specification is found, the skill will inform the user that the service type is not recognized and ask them to be more specific.
3.  The skill then uses the `telepath_service_qualification` tool to check if the service is available at the given address, using the service specification ID found in the previous step.
4.  The skill reports whether the service is available at the specified address.

## MCP Server Requirements

This skill requires an MCP server that provides service qualification and service specification listing capabilities.

**Required tools:** `telepath_service_qualification`, `telepath_list_service_specifications`

**Reference MCP Server:**

If you do not already have a locally configured MCP server that provides these tools, you can use the following reference endpoint:

*   Transport: HTTP
*   URL: `https://telepath.mcpgateway.online/mcp`

If you have your own MCP server that provides equivalent functionality, use that instead.

## Example Usage

User: Can you check if fiber is available at 123 Main Street, Anytown?

The skill will respond with either:

"Fiber service is available at 123 Main Street, Anytown."

or

"Fiber service is not available at 123 Main Street, Anytown."

or

"I could not find a service of that type. Could you be more specific?"

Overview

This skill checks whether a specified telecom or utility service is available at a given street address. It looks up a matching service specification and performs a qualification check against an MCP server, then returns an availability result. It's designed for fast, deterministic responses about service presence at a location.

How this skill works

First, the skill searches service specifications to find the ID that corresponds to the requested service type (for example, "fiber"). If a matching specification is found, it calls a service qualification endpoint with the address and specification ID. The skill interprets the qualification response and reports whether the service is available, unavailable, or if the request needs clarification.

When to use it

  • Pre-checking availability before sales or provisioning workflows
  • Customer support scripts to verify service options at a prospect address
  • Integrating into address validation and quoting tools
  • Automating eligibility checks in CRM or order-entry systems
  • Confirming coverage during field technician scheduling

Best practices

  • Provide a clear, specific service type (e.g., "fiber" vs "broadband") to improve matching accuracy
  • Send full address details: street number, street name, city, and postal code when possible
  • Handle the "service type not recognized" case by prompting the user for clarification
  • Cache service specification lists for short intervals to reduce repeated lookups
  • Validate and normalize addresses before calling the MCP server to reduce false negatives

Example use cases

  • "Is fiber available at 123 Main Street, Anytown?" returned as available/unavailable
  • Automated lead qualification: filter prospects by service availability at their address
  • Support agent verifying a new customer's eligibility during a phone call
  • Pre-provisioning check in an order flow to prevent orders for unsupported addresses

FAQ

What if the skill can't find a matching service type?

The skill will ask for a clearer or more specific service description. Try using standard terms like "fiber", "cable", "dsl", or the vendor service name.

Which MCP server does this use by default?

The skill can work with any MCP server that implements service specification listing and service qualification. If none is configured, a reference endpoint can be used as a fallback.