seven-mcp

Official

by seven-io

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

get_pricing

Retrieve pricing for SMS, voice, and other services by country code. Get results in JSON or CSV format.

Instructions

Get pricing information for SMS, voice, and other services

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pricing"
  }
}

Input Schema

Name	Required	Description	Default
`country`	No	Country code (ISO 3166-1 alpha-2) to get specific pricing
`format`	No	Response format

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 present, so the description carries full burden for behavioral disclosure. It only states 'Get pricing information' implying a read operation, but does not mention authentication needs, rate limits, default behavior (e.g., when no country is specified), or response structure. This is insufficient for full transparency.

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 a single sentence of 10 words, directly stating the tool's purpose with no redundancy. It is efficiently front-loaded and earns its place.

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 absence of an output schema and annotations, the description should provide more context about what the pricing information includes, how it is structured, and defaults. It falls short by not explaining output format or behavior when parameters are omitted, leaving the agent with an incomplete picture.

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 coverage is 100% as both parameters have descriptions in the input schema. The description adds no additional meaning beyond what is already in the schema, e.g., no clarification on the effect of omitting the country parameter. Baseline score of 3 applies.

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 clearly identifies the verb 'Get' and the resource 'pricing information' for SMS, voice, and other services. It distinguishes from sibling tools like get_balance or get_analytics, though 'other services' is vague. Overall, the purpose is clear but not maximally specific.

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 is provided on when to use this tool versus alternatives. The description does not mention when not to use it, prerequisites, or context for choosing this tool over similar ones like get_balance or lookup services. The agent is left to infer the use case without support.

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