Skip to main content
Glama

twilio_verify_check

Checks a Twilio Verify code a person received and returns whether it is approved, helping confirm user verification.

Instructions

(Beta) Check a code a person received from Twilio Verify (twilio_verify_send): answers whether it is approved.

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": "twilio_verify_check"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the '(Beta)' status and that the result is an approval verdict, but says nothing about attempt limits, code expiry, whether a failed check consumes attempts or incurs cost, or what errors look like — all material for a verification-check call.

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?

A single dense sentence: the beta flag, the action, the resource, the workflow link to the sibling, and the result semantic, with no filler wording. It is front-loaded on the verb and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and no parameters, the description is the only source of behavioral information, and it covers purpose and result but not failure modes, expiry, or attempt-consumption semantics. It is adequate to identify the tool but thin for a verification operation that mutates state on the Twilio side.

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?

The schema has zero parameters, so the baseline would be 4, but the description refers to an input ('a code a person received') that has no corresponding parameter, and it never explains how the code or verification target reaches the tool. That ambiguity is exactly the meaning the description needed to add and does not.

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 ('Check') and resource ('a code a person received from Twilio Verify') and explicitly ties it to the paired sibling twilio_verify_send, so an agent can distinguish it from send/list/lookup tools. It stops short of a 5 only because the outcome phrasing ('answers whether it is approved') is informal rather than naming the verification-status result.

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?

The parenthetical '(twilio_verify_send)' establishes the workflow context: this tool is used to validate a code that was previously sent by that sibling. There are no explicit exclusions or warnings about calling it before a send, but the usage context is clear enough for correct selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools