Skip to main content
Glama

AceRound AI Interview Copilot

unbind_sms_forwarder

Disconnect Android SMS forwarding; the apply assistant can no longer read codes from that phone until it is paired or bound again. Replies with the status as read back. (Requires the user's sign-in with scope 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": "unbind_sms_forwarder"
  }
}

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=false and destructiveHint=false; the description adds the concrete behavioral consequence (the assistant loses code-reading access), the reversibility condition (re-pair or re-bind), and the required auth scope job_applications:write. That is meaningful context beyond the annotations, though it does not address scope loss for other users or failure modes.

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?

Three short clauses, front-loaded with the action and its effect, then the re-binding condition, then return and auth details. No filler or repetition, and the auth requirement is properly parenthesized as secondary.

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 zero-parameter, non-destructive mutation with no output schema, the description covers the effect, reversibility, authorization, and a brief note on the response. A little more on whether existing forwarding configuration is preserved or lost would close the remaining gap.

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 and there is nothing for the description to disambiguate. The parenthetical auth-scope note adds operational context rather than parameter meaning.

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 (disconnect) and resource (Android SMS forwarding), with the effect on the apply assistant spelled out. It implicitly marks the inverse of binding/paring rather than naming the sibling bind_sms_forwarder_key tool, which is the only thing separating it from 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?

Usage is implied through the consequence: after calling this, codes cannot be read from that phone until it is paired or bound again, which tells an agent what situation this suits. There is no explicit when-not guidance and no named alternative for restoring forwarding, so guidance stays implicit.

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