Skip to main content
Glama
ponisha-mcp

ponisha-mcp

by Kia-Karami

ponisha_login_otp_verify

Verifies the SMS one-time password received by the user and stores the authenticated session to complete the login flow.

Instructions

Step 2 of SMS login: verify the code the user received by SMS and store the session.

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": {
      "mobile": "<mobile>",
      "otp": "<otp>"
    },
    "name": "ponisha_login_otp_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
otpYesThe code from the SMS
mobileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is partly covered. The description adds genuine value by disclosing that a session is stored as a side effect, but says nothing about invalid/expired code behavior, retry limits, or what a failed verification leaves behind.

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 sentence with zero filler, front-loaded with the flow position and followed by the action and side effect. Nothing needs trimming or reordering.

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 output schema, the description carries the burden of explaining the outcome, yet it only gestures at 'store the session' without saying whether a token/session id is returned or how failures surface. For a two-required-parameter auth step this is adequate but leaves the agent guessing about the result and error paths.

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 50%: 'otp' is documented in the schema and merely restated ('the code from the SMS'), while 'mobile' has no description anywhere. The description does not clarify mobile format (country code, must match the number used in the OTP request step), which is the one semantic an agent most needs here.

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?

The description gives a specific verb ('verify') plus the resource ('the code the user received by SMS') and states an additional effect ('store the session'). The 'Step 2 of SMS login' framing distinguishes it cleanly from the sibling ponisha_login_otp_request (step 1) and from ponisha_login_password.

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?

'Step 2 of SMS login' establishes the ordering prerequisite: an OTP must have been requested before this is called. It stops short of naming exclusions or pointing to ponisha_login_password / ponisha_session_status as alternatives, so it is clear context without routing guidance.

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