seven-mcp

Official

Overview Schema Source Related Servers Discussions Admin

update_number

Update a phone number's friendly name and configure forwarding for incoming SMS to phone numbers, email addresses, or Slack webhooks.

Instructions

Update phone number configuration including friendly name and forwarding settings

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": "update_number"
  }
}

Input Schema

Name	Required	Description
`number`	Yes	Phone number to update
`friendly_name`	No	Custom friendly name for the number
`sms_forward`	No	Phone numbers to forward incoming SMS to
`email_forward`	No	Email addresses to forward incoming SMS to
`slack_forward`	No	Slack webhook URL to forward incoming SMS to

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?

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Update' without mentioning whether the operation is destructive, requires permissions, or how it handles existing settings (replace vs. merge). This leaves significant behavioral ambiguity.

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, compact sentence with no unnecessary words. It efficiently conveys the core purpose without redundancy.

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 5 parameters, no output schema, and no annotations, the description is too sparse. It does not explain important context such as whether updates are additive or overwriting, any prerequisites (e.g., number must be owned), or the return value upon success. This leaves the agent with significant uncertainty.

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%, so the schema already documents all parameters. The description adds minimal value by naming 'friendly name and forwarding settings', which maps directly to schema properties. It does not provide additional syntax, defaults, or constraints beyond what the schema offers, resulting in a baseline score.

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 states the action ('Update') and the resource ('phone number configuration'), and lists the settings involved. While it doesn't explicitly differentiate from sibling tools, the resource is distinct from other update tools like update_contact, making the purpose sufficiently clear.

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 or any prerequisites. The description does not indicate when to update a number versus using other operations like order_number or delete_number.

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