Skip to main content
Glama
decentralized-usd

mcp-server-usdd

Official

psm_swap_from_usdd

Swap USDD for the PSM gem asset on a chosen network. Supports TRON, Ethereum, BSC, and testnets.

Instructions

Swap USDD into the PSM gem asset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketYes
amountYes
networkNoTarget network. Default: tron
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not address fees, slippage, required approvals, or side effects of the swap. The verb 'swap' implies a trade but lacks operational details.

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?

The description is a single sentence, which is concise, but it is too terse to be informative. It lacks structure and omits critical details, reducing its value despite its brevity.

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?

Given that the tool involves a swap with three parameters and no output schema, the description is incomplete. It does not explain return values, prerequisites, or operational flow, which is inadequate for an AI agent.

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 description coverage is only 33% (only the network parameter has a description). The description does not explain the 'market' or 'amount' parameters, leaving gaps that the schema alone does not fill.

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 clearly states the action (swap) and the resource (USDD into PSM gem asset), and it distinguishes from the sibling tool 'psm_swap_to_usdd' by specifying the direction (from USDD). However, the term 'gem asset' is ambiguous and could be more specific.

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?

No guidance on when to use this tool versus alternatives, such as the sibling psm_swap_to_usdd or other swap tools. The description does not provide context, prerequisites, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/decentralized-usd/mcp-server-usdd'

If you have feedback or need assistance with the MCP directory API, please join our Discord server