Skip to main content
Glama

面灵AI 面试助手

unbind_sms_forwarder

解除安卓短信转发的接入,之后网申 AI 不再能自动读取这台手机的验证码;需要时重新配对或绑定 key。回包为读回的状态。(需要用户授权,范围 job_applications:write)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With readOnlyHint=false and destructiveHint=false already supplied, the description adds real value: the loss of SMS-reading capability, the reversibility path, the authorization requirement and scope (job_applications:write), and the shape of the response (read-back status). Undisclosed edge behavior, such as whether it errors when nothing is bound or is idempotent, keeps it at 4.

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?

Front-loaded with the action and its consequence, followed by the remedy, the return value, and the auth note — every clause carries information. It is slightly dense with semicolon-joined clauses rather than cleanly separated sentences.

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 zero-parameter, no-output-schema mutation, the description covers the side effect, reversibility, authorization prerequisites, and return semantics. An agent has everything needed to call it correctly and to route the user to the recovery tool afterwards.

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 takes zero parameters and the schema is fully closed, so there is nothing for the description to disambiguate. Baseline of 4 applies; no parameter meaning is missing or contradicted.

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?

States a specific verb and resource ('unbind the Android SMS forwarding connection') plus the concrete downstream effect ('the job-application AI can no longer automatically read this phone's verification codes'), which separates it cleanly from bind_sms_forwarder_key and start_sms_relay_pairing.

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?

Implies when to call it (you want the AI to stop reading codes from this phone) and names the recovery path — re-pair or bind a key — which points the agent at the sibling tools. It does not name those siblings explicitly or state a when-not condition, keeping it just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources