Skip to main content
Glama
Sign In
Noves MCP Server

Noves MCP Server

Official
by Noves-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_wallet_summary

Get a clear summary of a wallet's recent activity across any blockchain network. Provide the wallet address and chain to receive key insights from transaction history.

Instructions

Get a comprehensive summary of wallet activity with key insights

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "<chain>",
      "walletAddress": "<walletAddress>"
    },
    "name": "get_wallet_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesBlockchain network
limitNoNumber of recent transactions to include in summary (default: 10)
walletAddressYesWallet address to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'comprehensive summary with key insights' but does not explain what insights are included, how the summary is computed, or whether it affects state. This is essentially a restatement of the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single sentence with no wasted words, but the phrases 'comprehensive' and 'key insights' are vague filler that reduce precision. Still, it is appropriately concise and front-loaded.

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

Completeness2/5

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

No output schema and no annotations exist, so the description must explain what the summary contains and how it differs from sibling tools like analyze_wallet. It fails to do so, leaving users unsure about the return format or the exact scope of 'wallet activity'.

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 description coverage is 100%, so each parameter is documented in the input schema. The description adds no additional meaning about the parameters or their relationships, keeping this at the baseline.

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 provides a 'comprehensive summary of wallet activity', identifying a specific verb and resource. However, it does not differentiate from sibling tools like analyze_wallet or get_recent_transactions, so it lacks sibling distinction.

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 guidance is provided on when to use this tool versus alternatives. The word 'summary' implies an overview use case, but there is no explicit context, exclusions, or mention of related tools.

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