Skip to main content
Glama

面灵AI 面试助手

test_sms_relay

测试短信转发:向登录招聘站使用的手机号发一条面灵验证码,最多等待 75 秒检查是否转发回来。不传 channel 时测试已接通的通路。(需要用户授权,范围 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": "test_sms_relay"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNo只测试这一条通路(选填)

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 the generic profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds real behavioral weight beyond them: an actual SMS is dispatched to a live phone number, the call blocks for up to 75 seconds, and it requires user authorization with the job_applications:write scope. The auth-scope and latency disclosures are exactly what an agent needs before invoking. It does not describe what happens on timeout or failure, keeping it below a 5.

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?

Two tight sentences with the action and its blocking behavior front-loaded, followed by the default-path and authorization caveats. No redundant or filler wording; every clause carries information.

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 no output schema, the description covers the side effect, the wait window, the default behavior, and the permission scope, which is sufficient to call it safely. The only gap is that the shape of the result (e.g. success/failure versus timeout) is only loosely implied by 'check whether it is forwarded back'.

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 coverage is 100% with a single enum parameter, so the baseline is 3. The description goes beyond the schema by explaining the semantic of omitting channel entirely — the tool then probes whichever path is already connected — which is not stated in the schema itself.

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?

States a specific verb and resource ('test SMS forwarding') and details the concrete mechanism: sends a verification code to the phone number used to log into the recruitment site, then waits up to 75 seconds. This is far beyond a restatement of the name. It does not explicitly name a sibling alternative (e.g. get_sms_relay_status for a passive check), so it falls short of a 5.

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?

The description implies the precondition that a forwarding path must already be connected ('tests the already-connected channel'), and the channel parameter's omission semantics are conveyed. However, there is no explicit statement of when to prefer this over get_sms_relay_status or start_sms_relay_pairing, and no when-not-to-use guidance.

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