Skip to main content
Glama
Sign In

NOTIFY

by io.github.n0t1fy
OverviewDiscussionsAdmin

Send a verification code that NOTIFY makes

start_verification
Idempotent

Verify a Georgian mobile number: NOTIFY makes a random six-digit code and sends it by SMS with a built-in template. The code is never shown to you: ask the human for the code they received, then call check_verification. A code works for 10 minutes and 5 checks, once; a new start for the same number replaces it.

With a test key (sk_test_), only the test numbers +995512345670 to +995512345679 are accepted and their code is always 000000; nothing is sent. At most 5 starts a minute go to one number, so spread test starts over the ten test numbers. +995512345671 simulates a refused SMS (status failed), +995512345672 an unreachable provider (error provider_unavailable: nothing was sent, retry with the same idempotency_key), +995512345673 an SMS that may or may not have arrived (still pending). With a live key it sends a real SMS and spends one credit.

replayed: true means this idempotency_key and request were already processed and no second SMS was sent; the verification it shows may say approved by then, which is not a check result. On too_many_verifications (5 an hour or 10 in a rolling 24 hours to one number), tell the human when they can try again (retry_at), and never retry by yourself.

Input Schema

NameRequiredDescriptionDefault
toYesThe phone number to verify, in E.164 format: `+9955` followed by eight digits. With a test key (`sk_test_`), only the test numbers +995512345670 to +995512345679 are accepted, and their code is always `000000`.
localeNoLanguage of the message: `ka` (Georgian, the default) or `en`.ka
api_keyNoAn sk_test_ key, for example from create_test_key. Leave it out to use the key in this MCP server's Authorization header. A live key (sk_live_) is refused here: tool arguments are kept in the conversation, so a live key belongs in the header.
templateNoWhich message carries the code. NOTIFY fills in the code, and the minutes where the template names them (10).verification_code
idempotency_keyYesA new unique value (a UUID) for each code you want sent. Reuse it only to retry the identical request: the retry then returns the original verification instead of sending a second SMS.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety/idempotency profile (readOnlyHint=false, idempotentHint=true, openWorldHint=true), and the description still adds substantial context beyond them: 10-minute/5-check code lifetime, one-time use, replacement semantics, test-key simulation behavior per test number, credit spend on live keys, `replayed: true` meaning, and the provider_unavailable retry rule with the same idempotency_key.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the check_verification handoff are front-loaded, and the test-key paragraph is a compact enumeration of edge cases. It is long and repeats the test-number range already present in the schema, but for a tool with this many failure modes most sentences earn their place.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so: it explains `replayed: true`, the `failed` status for a refused SMS, `provider_unavailable` as an error with retry guidance, `pending` as inconclusive, and `too_many_verifications` with `retry_at`. Rate limits (5 starts/minute, 5/hour, 10/24h) and auth requirements for live vs test keys are all covered.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: how idempotency_key interacts with `replayed: true`, that a new start replaces the previous code for the same number, and that the template determines the message that carries the code and the named 10-minute window. These are genuine semantic additions rather than restatement.

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?

Opens with a specific verb+resource ('Verify a Georgian mobile number') and immediately explains the mechanism: a random six-digit code sent by SMS via a built-in template. It also routes the agent to the natural sibling ('ask the human for the code they received, then call check_verification'), so the agent can distinguish this from check_verification without opening a 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 explicit when-to-use and when-not guidance: use check_verification after obtaining the human's code, use test numbers rather than one number for repeated test starts, and on too_many_verifications tell the human the retry_at time and 'never retry by yourself'. Alternatives and exclusions are both named.

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

All NOTIFY toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources