Skip to main content
Glama

面灵AI 面试助手

get_sms_relay_status

Read-only

查看短信验证码转发的接通状态:安卓「短信转发助手」是否已接入、iPhone 快捷指令最近一次推送时间、自检发往哪个号码、转发助手是否需要更新。网申 AI 登录招聘站时靠它自动取验证码。(需要用户授权,范围 job_applications:read)

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_sms_relay_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by stating the authorization requirement and the job_applications:read scope, which the agent needs before calling. It adds nothing on failure modes or refresh behavior, so the addition is modest.

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?

Two sentences, front-loaded with the verb and purpose, then a concrete enumeration of the status facets, closing with the call-site rationale and auth scope. The status list is dense but every item is meaningful and there is no filler.

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?

With no output schema and no parameters, the description carries the full burden of telling the agent what comes back, and it does so by enumerating the four status facets. Combined with annotations covering safety and the description stating the auth scope, an agent has everything needed to call it correctly.

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 there is no parameter semantics to explain and the baseline is 4. The description correctly spends no words on inputs.

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 opens with a specific verb+resource (查看…接通状态) and enumerates exactly what status facets are covered: Android forwarder connectivity, last iPhone Shortcut push time, self-test target number, and whether the forwarder needs an update. This is far more specific than a tautology. It stops short of naming a sibling to distinguish from (e.g. get_job_apply_client_status or test_sms_relay), so a 4 rather than 5.

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 gives a clear usage context: the job-application AI depends on this to automatically retrieve verification codes when logging into recruiting sites, which tells the agent when this status matters. It does not state exclusions or explicitly route to start_sms_relay_pairing / test_sms_relay when the status is bad, so it is clear context without alternatives.

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