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

crypto-payment-gateway-farsi

by plilian

فهرست دارایی‌های TheyPaid

theypaid_get_asset_catalog

Retrieves the configured asset list and current IDs for a TheyPaid store so you can use the correct identifiers when connecting a wallet or creating invoices.

Instructions

دارایی‌های فهرست تنظیم فروشگاه 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_get_asset_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the returned content (asset list plus each asset's current ID) but says nothing about read-only nature, authentication or store-scoping prerequisites, or whether IDs change over time beyond the word 'current'.

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?

Two short sentences, with the return content front-loaded and the usage note second. No waste, though the first sentence's phrasing ('assets of the store settings list') is slightly awkward and could be more direct.

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?

For a zero-parameter read tool with no output schema and no annotations, the description gives a partial return-value sketch but omits whether a store must be selected first and how the catalog differs from the supported-assets sibling, which is the most likely source of a wrong-tool call.

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 is nothing for the description to clarify, and it correctly implies a parameterless catalog fetch.

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?

A specific verb and resource: shows the store's configured assets and the current identifier of each. This is clearer than the name alone, but it never disambiguates from the sibling theypaid_get_supported_assets, which an agent could easily confuse it with.

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

Usage Guidelines3/5

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

It tells the agent what to do with the returned IDs ('use them when connecting a wallet or creating an invoice'), which implies downstream context, but it gives no guidance on when to call this tool versus theypaid_get_supported_assets or whether a store must already be selected.

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