Skip to main content
Glama

get_integration_snippet

Generate ready-to-paste code for adding Otipi phone/OTP login and SMS verification to Next.js, Supabase Auth, or Express projects, including Israeli SMS/2FA setup.

Instructions

Return ready-to-paste code for adding Otipi phone/OTP login to a project: Next.js App Router (API routes plus a client component), Supabase Auth (Send SMS hook setup plus client code) or Express. Works offline and does not need an API key. Use it when the user wants to integrate SMS verification or 2FA for Israeli numbers.

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": {
      "framework": "<framework>"
    },
    "name": "get_integration_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoCode language. Default ts.ts
frameworkYesTarget framework.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden, and it does disclose the operationally important facts: works offline, requires no API key, and what each target produces (API routes plus a client component; Send SMS hook setup plus client code). It stops short of stating that output is static/read-only with no side effects, which would fully close the gap for an unannotated tool.

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?

Two sentences, front-loaded with the capability and backed by the supported targets and the usage trigger. Every clause carries information; nothing is repetitive or padded.

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 two-enum, no-output-schema tool this is nearly complete: it states the purpose, the targets, the side conditions (offline, no key) and the usage trigger. The only soft spot is that it does not characterize the response shape (e.g., one snippet per call versus multiple files), which matters somewhat given no output schema exists.

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% and both parameters are enums with descriptions, so the baseline would be 3. The description earns above that by explaining what each framework value yields (Next.js App Router vs. Supabase Auth vs. Express), which is meaning the enum labels alone do not convey.

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?

"Return ready-to-paste code for adding Otipi phone/OTP login to a project" gives a specific verb (return code) and resource (integration snippet), then enumerates the three supported targets. This reads clearly as a code-generation tool, distinct from the operational siblings like send_test_otp or verify_otp.

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?

"Use it when the user wants to integrate SMS verification or 2FA for Israeli numbers" gives a concrete triggering condition. There is no explicit when-not or a named alternative, but the generation-vs-execution split from the sibling tools is obvious enough that this is a clear usage statement rather than an implied one.

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