Skip to main content
Glama

Confirm a phone contact

confirm_notification_contact
Idempotent

Confirms an sms or voice contact, added before they were retired, with the 6-digit code it was texted or told in a call. The code works for 24 hours and 5 tries. Ask the phone's owner for it; never guess.

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": {
      "id": "<id>",
      "code": "<code>"
    },
    "name": "confirm_notification_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesContact ID from add_notification_contact or list_notification_contacts.
codeYesThe 6-digit code the phone received.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / code / description
      Added value: +"The 6-digit code the phone received."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior. The description adds genuine substance beyond that: a 24-hour code lifetime and a 5-attempt limit, both of which change how an agent should sequence and retry calls. It does not say what the tool returns or what failure looks like after the fifth try, but for a two-parameter action the added context is solid.

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 sentences, front-loaded with the action and credential, then constraints, then a safety rule. No redundant wording and nothing that restates the annotations verbatim.

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 simple two-parameter confirmation with a fully documented schema and no output schema, the description covers lifetime, attempt budget, and where to obtain the secret. The only gap is what a successful or exhausted confirmation produces, which is minor given the tool's narrow scope.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters carry their own descriptions, so the schema already does the work. The description reinforces that the code is the one sent to the phone and adds the 6-digit/24-hour framing, but adds no new syntax or format detail beyond the pattern already declared.

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 ('Confirms') and resource ('an sms or voice contact'), plus the credential used (the 6-digit code it was texted or told in a call). This clearly separates it from creation (add_notification_contact) and listing tools, though it never names a sibling such as test_notification_contact explicitly.

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?

Gives the operative precondition — only contacts 'added before they were retired' can be confirmed — and a procedural rule ('Ask the phone's owner for it; never guess'), which steers the agent away from brute-forcing the code. It stops short of stating alternative tools or when confirmation is preferable to testing.

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