Skip to main content
Glama

AceRound AI Interview Copilot

get_sms_relay_status

Read-only

Show SMS code forwarding status: whether the Android SMS forwarder is connected, when the iPhone shortcut last pushed, and whether the forwarder app needs an update. The apply assistant uses it to read sign-in codes. (Requires the user's sign-in with scope 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
Behavior4/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 genuinely new context by stating the required sign-in and the job_applications:read scope. It also discloses which state dimensions come back, so the caller knows what 'status' means. It does not discuss staleness windows or failure modes (e.g., what it reports when the forwarder was never bound).

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 sentences, front-loaded with the resource and its reported facets, with the auth prerequisite demoted to a trailing parenthetical. No redundant restatement of the name and no filler.

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?

With no output schema, the description carries the return-value burden and does so by naming the three status facts. That is enough for a zero-parameter read tool, though it stops short of describing the shape or possible values of those fields, leaving some ambiguity about how 'needs an update' is encoded.

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; nothing in the schema needs elaboration and the description correctly spends no words on argument syntax.

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 ('Show SMS code forwarding status') and enumerates the three facets reported: Android forwarder connectivity, last iPhone shortcut push time, and whether an update is needed. It reads clearly as a read-only status probe distinct from siblings like bind_sms_forwarder_key or unbind_sms_forwarder, though it never contrasts itself with the other '*_status' siblings by name.

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 gives a usage context ('The apply assistant uses it to read sign-in codes'), which implies when the caller would reach for it. However, there is no explicit when-not guidance and no routing to alternatives such as get_job_apply_client_status or get_voiceprint_status, so the selection logic is left inferential.

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