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

crypto-payment-gateway-farsi

by plilian

نمای کلی حساب TheyPaid

theypaid_get_account

Reads the connected account's stores and service-credit balance used for invoice processing fees, separate from the acceptor wallet's crypto.

Instructions

فروشگاه‌ها و موجودی اعتبار خدماتی حساب متصل را می‌خواند. اعتبار خدماتی برای کارمزد پردازش فاکتور است و با رمزارز کیف‌پول پذیرنده تفاوت دارد.

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_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'reads' implies a safe read-only operation with no mutation, and the note about service credit versus wallet crypto adds useful domain context. However, it does not mention authentication/connection prerequisites beyond 'connected account', nor return shape or any limits.

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?

The description is two sentences and front-loads the core purpose. The second sentence adds useful disambiguation about service credit versus wallet cryptocurrency, though it could be slightly tighter.

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 zero parameters and no output schema, the description does a reasonable job stating that stores and service credit balance are read. It stops short of describing the account-overview response structure or connection prerequisites, which leaves some contextual gaps for an agent invoking it cold.

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?

The tool takes zero parameters, so the baseline is 4. There are no parameter semantics to clarify, and the description appropriately focuses on what the operation returns rather than on nonexistent inputs.

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?

The description uses a specific verb ('reads') and names the resources: stores and service credit balance for the connected account. It also clarifies that service credit is distinct from the merchant wallet's cryptocurrency. It does not explicitly differentiate itself from siblings like theypaid_get_credit or theypaid_list_stores, which keeps it from a 5.

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?

There is no explicit guidance on when to use this tool versus alternatives such as theypaid_get_credit or theypaid_list_stores. The overview nature is implied by the title and by reading both stores and credit, but no exclusions or routing conditions are stated.

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