Skip to main content
Glama

AceRound AI Interview Copilot

bind_sms_forwarder_key

Connect Android SMS forwarding with the key (starting with sk_) the user copied from the SMS forwarder app home screen; the key is verified first. (Requires the user's sign-in with scope job_applications:write.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "bind_sms_forwarder_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare that the tool is a non-destructive, closed-world write (readOnlyHint=false), and the description adds genuinely useful context beyond them: the key is validated before the binding is applied, and the call requires an authenticated session with a specific OAuth scope. It doesn't say what happens on verification failure, or whether an existing binding is replaced, which keeps it from 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?

One main clause plus a single parenthetical for the auth prerequisite; the key format and provenance are front-loaded where the agent needs them. Nothing is redundant with the schema or the annotations.

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, no-output-schema binding tool, the description covers provenance, validation, and the auth scope — the essentials for calling it correctly. It omits the post-binding state (does it overwrite an existing forwarder key, what an invalid key returns), which leaves a small but real 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?

Schema coverage is 0% (the single parameter is just a 1-200 char string), so the description carries the burden — and it does, specifying the sk_ prefix convention and the exact UI location the value comes from. It adds no guidance on trimming, revocation, or how to recover a mis-pasted key, so it is strong but not exhaustive.

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 names a concrete verb and resource ('Connect Android SMS forwarding') and pins down which key is meant ('the key (starting with sk_) the user copied from the SMS forwarder app home screen'). An agent can distinguish this from the sibling unbind_sms_forwarder without opening the 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 gives a clear precondition for invocation: the user must have copied an sk_ key from the forwarder app's home screen, and the caller must be signed in with the job_applications:write scope. It does not state when NOT to use it or explicitly point to unbind_sms_forwarder / get_sms_relay_status for the opposite operation, so this stops short of full routing 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