Skip to main content
Glama
crypto-payment-gateway-farsi

crypto-payment-gateway-farsi

by plilian

اتصال به حساب TheyPaid

theypaid_connect_account

Connects to a TheyPaid account using credentials configured in the MCP server environment. Passwords and access tokens are not accepted or returned; complete two-factor codes separately.

Instructions

با اطلاعات ورودی تنظیم‌شده در محیط امن سرور MCP وارد حساب TheyPaid می‌شود. گذرواژه و توکن دسترسی به‌عنوان ورودی ابزار پذیرفته یا در پاسخ بازگردانده نمی‌شوند. اگر ورود دومرحله‌ای فعال باشد، مرحلهٔ کد یک‌بارمصرف را جداگانه تکمیل کنید.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "theypaid_connect_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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, the description carries the full burden and does well: it discloses that credentials come from the server's secure environment, that passwords/tokens are neither accepted as input nor returned, and that 2FA is handled out-of-band. It omits what happens on failure, whether an existing session is superseded, and whether the call is idempotent/repeatable.

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 short sentences, front-loaded with what the tool does, followed by the security constraint and the 2FA handoff. Every sentence adds information an agent needs; nothing is 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 no-parameter, no-output-schema login tool with no annotations, this covers the essentials: credential source, non-disclosure, and the 2FA split. Remaining gaps are the return signal (success vs. 2FA-required) and interaction with an existing session, which a sibling like theypaid_check_connection could clarify but the description does not.

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?

Zero parameters, which is the baseline-4 case. The description adds useful meaning by explaining why the schema is empty – credentials are pre-configured in the server environment rather than passed by the caller.

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 ('وارد حساب TheyPaid می‌شود' – logs into the TheyPaid account), and explicitly distinguishes itself from the two-factor sibling by saying the OTP step is completed separately. An agent can route to theypaid_complete_two_factor versus this tool without opening either schema.

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?

Explicitly routes the 2FA case to a separate step, naming the condition (two-factor enabled) and the action (complete OTP separately). It stops short of stating that this must be called before store/wallet/payment operations or that it replaces an existing session, so usage context is clear but not exhaustive.

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