Skip to main content
Glama

connect_info

Retrieve environment details including accessible wallets, policies, and capabilities to understand available crypto operations before proceeding.

Instructions

Get self-discovery info: accessible wallets, policies, capabilities, and AI-ready prompt. Call this first to understand your environment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration and handler for connect_info which wraps the GET /v1/connect-info endpoint.
    export function registerConnectInfo(server: McpServer, apiClient: ApiClient): void {
      server.tool(
        'connect_info',
        'Get self-discovery info: accessible wallets, policies, capabilities, and AI-ready prompt. Call this first to understand your environment.',
        {},
        async () => {
          const result = await apiClient.get('/v1/connect-info');
          return toToolResult(result);
        },
      );
    }
Behavior3/5

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

With no annotations provided, description carries full burden. It discloses what data is returned (compensating for missing output schema), but omits safety profile (read-only vs destructive), authentication requirements, or rate limit characteristics that agents need for a discovery endpoint.

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?

Two sentences, zero waste. Front-loaded with verb and scope. First sentence enumerates return values; second provides usage context. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter discovery tool, description adequately compensates for missing output schema by listing the four key data categories returned (wallets, policies, capabilities, AI-ready prompt). Completeness is strong given low complexity, though output format details would elevate it further.

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?

Zero parameters present; input schema is unambiguous empty object. Description appropriately makes no param claims. Baseline 4 applies as there are no parameters requiring semantic clarification.

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?

Uses specific verb 'Get' with concrete resource list (wallets, policies, capabilities, AI-ready prompt). Successfully positions tool as the discovery/orientation entry point via 'Call this first', distinguishing it from specific getters like get_policies or get_wallet_info, though it does not explicitly name those siblings.

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?

Provides explicit temporal guidance ('Call this first to understand your environment') establishing when to use it relative to other operations. Lacks explicit 'when not to use' guidance or named alternative tools for specific queries.

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/minhoyoo-iotrust/WAIaaS'

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