Skip to main content
Glama

north_received

Check what has been received on a specified wallet address, including amounts, blocks, and confirmation depth for each deposit.

Instructions

What sits on one of this wallet's own addresses, in blocks, and how deep it is.

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": {
      "address": "<address>"
    },
    "name": "north_received"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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. It implies a read-only lookup and hints that results include block placement and confirmation depth, but says nothing about return shape, error behavior when the address is not wallet-owned, or result ordering/limits.

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

Conciseness3/5

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

It is a single short sentence with no filler, but the terseness costs clarity: the elliptical phrasing ("what sits on," "in blocks") reads as a riddle rather than a front-loaded statement of capability.

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?

For a one-parameter query tool with no annotations and no output schema, the description should at minimum say what is returned and in what form. As written, an agent cannot tell whether it gets a list of received outputs, a count, or per-block detail beyond the vague "how deep it is."

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 coverage is 0%, so the single "address" parameter is undocumented structurally. The description partially compensates by constraining it to "one of this wallet's own addresses," which is real semantic value, though it does not state the expected address format or network.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"What sits on one of this wallet's own addresses, in blocks, and how deep it is" gestures at a read of received items on an address with block/confirmation depth, but there is no verb and no resource noun naming the object (utxos? payments? outputs?). It is distinguishable from north_balance or north_pay only by inference, not by explicit statement.

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?

The phrase "one of this wallet's own addresses" is the only guidance, implying the lookup is restricted to wallet-owned addresses rather than arbitrary ones. There is no when-to-use framing and no routing against siblings such as north_history or north_address, which an agent would plausibly confuse with this tool.

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