Skip to main content
Glama
ZhipingYang

TelePath PSTN MCP

by ZhipingYang
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.2.0

  • Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap. The tool's purpose as a setup/help guide is clear, though it is not a domain operation.

    Naming Consistency5/5

    A single tool cannot exhibit inconsistency. The name telepath_setup_help follows a clear snake_case convention, which is acceptable.

    Tool Count1/5

    The server is named 'TelePath PSTN MCP' but exposes only a setup help tool, not a single actual PSTN operation. This is a severe under-scoping for the apparent domain.

    Completeness1/5

    The tool surface is almost empty. There are no tools for making calls, managing numbers, or any other PSTN functionality. The setup help tool does not contribute to the server's intended purpose.

  • Average 4/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior3/5

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

    No annotations are provided, so the description bears full responsibility for disclosing behavior. It communicates that the tool surfaces setup instructions, but it doesn't explicitly state that the tool performs no configuration itself or describe the output format. The instructional tone implies it's informational, but this could be more explicit.

    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 concise and well-structured, using a warning icon, bulleted list of environment variables, and numbered configuration steps. Every element serves a purpose, and the most critical information (missing configuration) is front-loaded.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness5/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    For a setup-help tool with no parameters, no output schema, and no annotations, the description fully covers the necessary context: the problem, the specific environment variables needed, and two ways to set them. It is self-contained and complete for its intended use.

    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?

    The tool has zero parameters, and the schema is empty. According to the rubric, 0 params earns a baseline score of 4. The description adds no parameter details simply because there are none to explain.

    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 description explicitly states the tool's purpose: addressing TelePath not being configured and instructing the user to set environment variables. It names the specific resources (TELEPATH_USERNAME, TELEPATH_PASSWORD) and provides actionable steps, making the intent unambiguous even without sibling tools.

    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 clearly defines the context in which this tool is relevant: when TelePath is unconfigured. It lists two concrete configuration methods, giving the agent and user clear usage guidance. While it doesn't mention alternatives or exclusions, the absence of siblings makes this acceptable.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

telepath-pstn-mcp MCP server

Copy to your README.md:

Score Badge

telepath-pstn-mcp MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ZhipingYang/telepath-pstn-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server