Skip to main content
Glama

面灵AI 面试助手

bind_sms_forwarder_key

用用户在「短信转发助手」App 首页复制的 key(sk_ 开头)接通安卓短信转发,绑定前会校验 key 是否有效。(需要用户授权,范围 job_applications:write)

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": {
      "key": "<key>"
    },
    "name": "bind_sms_forwarder_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, closed-world; the description adds real behavioral context beyond that — the key is validated before binding and user authorization with the job_applications:write scope is required. It does not say what happens on validation failure or whether binding replaces an existing forwarder, leaving some gaps.

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?

One front-loaded sentence states the action and the key's source, then a parenthetical adds the authorization scope. No filler or repetition; every clause adds information an agent needs.

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 one-parameter tool with annotations present and no output schema, the definition covers input provenance, validation behavior, and auth scope adequately. Minor omissions remain: the result of binding, failure behavior on an invalid key, and effect on any existing binding.

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?

Schema description coverage is 0%, so the description carries the burden and does so well: it specifies the key originates from the App home page, has the sk_ prefix, and is validated. It doesn't state format details such as length limits (the schema's 1-200), but the essential provenance and validation semantics are covered.

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 names a specific verb and resource: bind an SMS-forwarder key (sk_ prefix, copied from the 「短信转发助手」App home page) to connect Android SMS forwarding. That is far more specific than the tool name alone, though it never contrasts itself with nearby siblings such as start_sms_relay_pairing or unbind_sms_forwarder.

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?

It supplies a prerequisite (the user must copy the key from the App home page) and an authorization requirement (scope job_applications:write), which are useful before invoking. It gives no explicit when-to-use vs when-not guidance or alternatives, so an agent must infer that this is the binding step distinct from pairing/unbinding.

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