Skip to main content
Glama

面灵AI 面试助手

start_sms_relay_pairing

为安卓手机生成短信转发的配对码(20 分钟有效):用户在手机上打开回包中的链接下载「短信转发助手」,打开后输入配对码即接通。接通后用 get_sms_relay_status 确认。(需要用户授权,范围 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": "start_sms_relay_pairing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, which only say this is a non-read-only, non-destructive, closed-world call, the description adds real behavioral detail: the code expires after 20 minutes, the reply contains a download link the user must open, the code is entered inside the app, and the auth scope job_applications:write is required. Those are exactly the operational facts an agent needs, and none of them are duplicated from structured fields.

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 front-loads the action and its validity window, then walks through the steps, with the authorization scope tucked into parentheses. It is dense but every clause (TTL, link, code entry, status check, scope) carries information, so there is little waste.

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?

Although there is no output schema, the description tells the agent what comes back (a link plus a pairing code), what to tell the user to do with it, how to confirm success, and what authorization is needed. For a zero-parameter setup tool, that is sufficient end to end.

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, so the baseline is 4; there is nothing for the description to disambiguate. It does note that the reply is a '回包' containing a link, which usefully frames the output even though the input side is empty.

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?

The description states a specific verb and resource (generate an SMS-forwarding pairing code for an Android phone) and pins down the scope: the code is valid for 20 minutes and is redeemed inside the 短信转发助手 app. That is enough to distinguish it from siblings such as bind_sms_forwarder_key, test_sms_relay, and get_sms_relay_status without opening any schema.

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?

It clearly describes the situation that warrants the call (onboarding an Android phone for SMS forwarding) and the sequence: give the user the link and code, then verify with get_sms_relay_status. It does not say when not to call it or when to prefer bind_sms_forwarder_key or test_sms_relay instead.

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