Skip to main content
Glama
mission69b

t2000

by mission69b
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

t2000_deposit_info

Retrieve deposit instructions including wallet addresses, supported networks, and accepted assets to fund or top up your account.

Instructions

Get deposit instructions — wallet address, supported networks, accepted assets. Use when the user asks how to fund or top up their account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • packages/mcp/src/tools/read.ts:182-194 (handler)
    The handler for the 't2000_deposit_info' tool is implemented within the 'registerReadTools' function in 'packages/mcp/src/tools/read.ts'. It invokes the 'agent.deposit()' method and returns the serialized result as a tool response.
    server.tool(
  't2000_deposit_info',
  'Get deposit instructions — wallet address, supported networks, accepted assets. Use when the user asks how to fund or top up their account.',
  {},
  async () => {
    try {
      const result = await agent.deposit();
      return { content: [{ type: 'text', text: JSON.stringify(result) }] };
    } catch (err) {
      return errorResult(err);
    }
  },
);

Tool Definition Quality

A3.8/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 burden. It describes what information will be retrieved (deposit instructions) but doesn't disclose behavioral aspects like rate limits, authentication requirements, error conditions, or response format. The description is accurate 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is perfectly concise with two sentences that each serve a clear purpose: the first states what the tool does, the second states when to use it. There's no wasted language or redundancy.

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 informational tool with no annotations and no output schema, the description provides adequate basic context about what information will be returned. However, it doesn't describe the structure or format of the returned deposit instructions, which would be helpful given the lack of output schema.

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 has 0 parameters with 100% schema description coverage. The description doesn't need to explain parameters, and it appropriately focuses on the tool's purpose instead. This meets the baseline for zero-parameter tools.

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 tool's purpose with specific verbs ('Get deposit instructions') and resources ('wallet address, supported networks, accepted assets'). It doesn't explicitly differentiate from siblings like 't2000_balance' or 't2000_fund_status', but the specificity of deposit instructions provides some implicit distinction.

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?

The description provides clear context for when to use this tool ('when the user asks how to fund or top up their account'). It doesn't specify when NOT to use it or name explicit alternatives among siblings, but the usage context is well-defined and practical.

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/mission69b/t2000'

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