Skip to main content
Glama
Sign In
Ninja MCP

Ninja MCP

by Khaled-Harthi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Submit STC Pay OTP

ninja_submit_stc_otp

Submits an STC Pay OTP to finalize payment and place the order. Requires a fresh OTP and confirmation to execute the live payment submission.

Instructions

Submit an STC Pay OTP. This can complete payment and place the order.

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": {
      "confirmSubmitOtp": "<confirmSubmitOtp>",
      "otp": "<otp>"
    },
    "name": "ninja_submit_stc_otp"
  }
}

Input Schema

NameRequiredDescriptionDefault
otpYesFresh STC Pay OTP.
pollCountNo
confirmSubmitOtpYesSet true to run the live payment submission.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Lacks annotations. Description only says 'submit' and 'complete payment' without disclosing side effects, idempotency, authorization needs, or error behavior. Minimal behavioral context.

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

Conciseness3/5

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

Two sentences, very concise with no fluff. However, it is under-specified and omits important context, making conciseness a trade-off with completeness.

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

Completeness2/5

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

No output schema. Description does not cover return values, error states, pollCount behavior, or what happens after successful submission. Incomplete for a payment confirmation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% (no description for pollCount). Description adds no parameter details beyond what schema provides, failing to compensate for the missing pollCount description.

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?

Description clearly states the action (submit OTP) and outcome (complete payment and place order). It distinguishes from siblings like ninja_initiate_stc_pay by implying finalization, but does not explicitly differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

Provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., must have initiated STC Pay first), and no context about ordering in a payment flow.

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