Skip to main content
Glama

Mon wallet Déjà

deja_wallet_info

Retrieve the agent's wallet address for USDC funding, or get clear instructions to create one if no wallet exists.

Instructions

Affiche l'adresse du wallet de cet agent (pour l'alimenter en USDC) ou explique comment en créer un.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deja_wallet_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It implies the operation is informational and says the fallback is to explain how to create a wallet rather than creating one, which suggests no side effects, but it never states that the call is read-only or whether calling it could provision a wallet. It also says nothing about error conditions or about what happens when no wallet exists.

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?

It is a single sentence that states the primary result first and then the conditional fallback. There is no filler, and nothing is buried.

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-argument, no-output-schema info tool, the description covers both possible outcomes (address, or creation instructions) and the motivation for each. The remaining gap, namely whether invoking the tool has any side effect when no wallet exists, is minor but real for an agent deciding whether to call it.

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 takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and it does not waste words on argument semantics.

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 gives a specific verb and resource in stating that it displays this agent's wallet address, and adds the reason (funding with USDC) plus a fallback of explaining how to create a wallet. This is clear enough for an agent to understand what the tool is for. It does not explicitly contrast the tool with deja_lookup or deja_publish, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool by naming the use case of funding the wallet with USDC, and it mentions the case where the agent has no wallet yet. However, it does not state explicit triggers (for example, 'call this when the user asks for the deposit address'), does not say when not to use the tool, and does not route to any alternative.

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

Deploy Server

Other Tools