Skip to main content
Glama

Code by SMS

send_verification_sms

Only when the learner asks for it: text a 6-digit code to their phone (EU/EEA/CH/UK, international format like +49 170 1234567); then call confirm_email with it. This confirms the phone, not the e-mail address; the number is not stored.

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": {
      "phone": "<phone>"
    },
    "name": "send_verification_sms"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, openWorld and non-idempotent, and the description adds what annotations cannot: the required two-step flow with confirm_email, the geographic restriction (EU/EEA/CH/UK), and the privacy fact that the number is not stored. It does not cover code expiry, resend limits, or failure modes such as an unsupported region.

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 compact clauses with the gating condition front-loaded, then the action, then the follow-up call. No filler and nothing buried mid-sentence that an agent would need early.

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 tool with no output schema, the definition covers trigger, format, region, verification scope, privacy outcome, and the required next call. Only operational details like expiry window, rate limits, or delivery-failure handling are absent.

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% and the single parameter is undocumented there, so the description carries the burden — and it does, specifying the phone format with a worked example (+49 170 1234567) and the accepted regions. It stops short of stating validation behavior for malformed or non-EU numbers.

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?

States a specific verb and resource — "text a 6-digit code to their phone" — and immediately scopes what the action actually verifies ("confirms the phone, not the e-mail address"). An agent can distinguish this from confirm_email and the read-only sibling tools 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition ("Only when the learner asks for it") which functions as a when-not-to-use rule, plus a concrete follow-up requirement ("then call confirm_email with it"). The sequencing between the two tools is spelled out rather than inferred.

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