Skip to main content
Glama

north_history

Retrieve the local NORTH wallet’s summarized transaction history, newest first, to review recent payments and balance movements without exposing recovery words.

Instructions

The wallet's movements as its server sums them up, newest first.

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": "north_history"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that results are ordered newest first and framed from the server's perspective, but says nothing about read-only safety, result limits, pagination, time-range coverage, or what an empty wallet returns.

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?

A single short sentence with no padding, and the ordering detail is placed early. The brevity is slightly costly, however, because the vague phrasing 'as its server sums them up' consumes words without adding precision.

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?

For a zero-parameter read tool with no output schema, the definition conveys the resource and its sort order, which is close to sufficient. It still leaves open whether output is paginated or truncated and how far back history extends, gaps the agent can only discover by calling.

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 there is no parameter meaning to convey; the baseline for a parameterless tool applies. The description does not need to compensate for any schema gap here.

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?

The phrase 'the wallet's movements' suggests a transaction/activity listing and 'newest first' fixes the ordering, but the definition is written as a noun phrase with no verb and only loosely distinguishes it from siblings such as north_received or north_payments. 'As its server sums them up' is idiosyncratic wording that does not clarify whether the result is a raw ledger, an aggregated summary, or both.

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?

There is no statement of when to call this instead of north_received, north_payments, or north_balance, and no prerequisites or exclusions are given. The agent must infer that this is the general activity feed from the word 'history' alone.

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