seven-mcp

Official

by seven-io

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

order_number

Buy a virtual phone number with monthly or annual payment intervals for SMS, voice, and RCS messaging.

Instructions

Purchase a phone number

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": {
      "number": "<number>"
    },
    "name": "order_number"
  }
}

Input Schema

Name	Required	Description	Default
`number`	Yes	Phone number to purchase
`payment_interval`	No	Payment interval for the number (default: annually)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1May 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'Purchase a phone number' without disclosing effects on balance, required permissions, error conditions, or what happens if the number is already owned. This is insufficient for an AI agent to understand side effects.

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?

The description is a single sentence with no wasted words. It is front-loaded and concise. However, it could be slightly expanded to include critical context without losing conciseness.

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

Completeness2/5

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

Given the tool has 2 parameters, no output schema, and no annotations, the description is incomplete. It fails to mention return values, error handling, or how it integrates with sibling tools like 'get_available_numbers' and 'get_active_numbers'. Essential context is missing.

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 both parameters. The description adds no additional meaning beyond the schema; it does not explain how the parameters relate to the purchase action. Baseline score of 3 is appropriate.

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 'Purchase a phone number' clearly states the action (purchase) and resource (phone number). It distinguishes from sibling tools like 'get_number', 'update_number', and 'delete_number' by indicating ownership acquisition. However, it lacks specificity about the ordering process or outcome.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'get_available_numbers' or 'get_active_numbers'. The description does not mention prerequisites or related tools, leaving the agent without context for proper selection.

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