Skip to main content
Glama

t2000_address

Retrieve the Sui wallet address for an AI agent to receive funds, enabling autonomous financial transactions within the t2000 banking system.

Instructions

Get the agent's Sui wallet address for receiving funds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the t2000_address tool which retrieves the agent's Sui address.
    server.tool(
      't2000_address',
      "Get the agent's Sui wallet address for receiving funds.",
      {},
      async () => {
        try {
          const address = agent.address();
          return { content: [{ type: 'text', text: JSON.stringify({ address }) }] };
        } catch (err) {
          return errorResult(err);
        }
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 discloses the tool's purpose as a read operation to retrieve an address, which is straightforward, but lacks details on behavioral traits like error conditions, permissions needed, or response format. The description is accurate but minimal, leaving gaps in behavioral context.

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, clear sentence that front-loads the essential information without any wasted words. It efficiently conveys the tool's purpose in a compact form, making it easy to understand at a glance.

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 tool's simplicity (0 parameters, no annotations, no output schema), the description is adequate but minimal. It explains what the tool does but does not cover potential complexities like return value format or error handling. For a basic read operation, it's complete enough to be functional but lacks depth for richer contextual understanding.

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 input schema has 0 parameters with 100% coverage, so no parameter information is needed. The description appropriately does not discuss parameters, focusing solely on the tool's purpose. This meets the baseline for tools with no parameters, as it avoids unnecessary detail.

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 clearly states the specific action ('Get') and resource ('agent's Sui wallet address for receiving funds'), distinguishing it from sibling tools like t2000_balance or t2000_send which handle different operations. It precisely communicates what the tool does without ambiguity.

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 implies usage context ('for receiving funds'), suggesting it should be used when the agent needs their wallet address to accept payments or deposits. However, it does not explicitly state when not to use it or name alternatives, such as if other tools might provide related address information.

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