@striderlabs/mcp-spectrum

get_account_overview

Retrieve your Spectrum account overview to view current plan, balance due, payment due date, and data usage summary in one place.

Instructions

Get Spectrum account overview including current plan, balance due, payment due date, and data usage summary.

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": {
      "username": "<username>",
      "password": "<password>"
    },
    "name": "get_account_overview"
  }
}

Input Schema

Name	Required	Description	Default
`password`	Yes	Spectrum account password
`username`	Yes	Spectrum account username or email address

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

There are no annotations, so the description carries the behavioral burden. 'Get' signals a read-only operation and the listed outputs clarify what is returned, but it does not mention side effects, credential sensitivity, or that no account changes are made. This is adequate but lacks deeper behavioral context.

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?

A single sentence that is front-loaded with the action and resource, followed by a compact list of returned items. There is no redundant wording or filler.

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 simple two-parameter read operation, the description covers the main return values and the schema covers inputs. It lacks explicit sibling differentiation and output formatting details, but those are less critical given the tool's low complexity and clear scope.

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%, and both username and password already have clear descriptions. The tool description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 uses a specific verb 'Get' with a clear resource, 'Spectrum account overview,' and explicitly lists the returned information: current plan, balance due, payment due date, and data usage summary. This distinguishes it from siblings like pay_bill, check_outages, and schedule_technician.

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

Usage Guidelines3/5

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

The contents imply use when an agent needs a summary of account status, plan, balance, due date, or data usage. However, it does not explicitly say when to use this tool over get_bill_history or get_service_details, nor does it mention alternatives or exclusion cases.

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

Deploy Server