Skip to main content
Glama
stables-money

Stables MCP Server

Official

reactivate_virtual_account

Re-enable a deactivated virtual account to resume stablecoin payments and transactions. Provide the customer ID and virtual account ID to restore access.

Instructions

Reactivate a previously deactivated virtual account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesThe customer ID
virtualAccountIdYesThe virtual account ID to reactivate
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It only states the action ('reactivate'), without mentioning authorization needs, side effects, or state changes beyond the obvious.

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?

The description is a single, concise sentence with no unnecessary words. It effectively communicates the tool's purpose.

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?

Given the simplicity of the tool (2 params, no output schema), the description is minimally adequate but lacks additional context such as prerequisites or effects. It does not fully compensate for missing annotations.

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

Parameters3/5

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

Schema coverage is 100% with clear parameter descriptions. The tool description adds no extra meaning beyond what the schema provides, so baseline score of 3 applies.

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?

The description uses a specific verb ('Reactivate') and resource ('previously deactivated virtual account'), clearly distinguishing it from sibling tools like 'deactivate_virtual_account' and 'create_virtual_account'.

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 explicit guidance on when to use this tool versus alternatives. It implies it is the reverse of 'deactivate_virtual_account', but provides no when-to-use or when-not-to-use instructions.

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/stables-money/mcp-server'

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