Skip to main content
Glama

north_wait

Waits for a NORTH wallet address to reach a specified amount, returning paid true or false within a default 120-second timeout (300 max).

Instructions

Waits until one of this wallet's addresses holds an amount, at most timeout_seconds (300 at most, 120 if not given). Answers paid true or false.

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>",
      "amount": "<amount>"
    },
    "name": "north_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesNORTH, as text
addressYes
confirmationsNo
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it declares the tool blocks until a condition is met, discloses the timeout ceiling (300) and the default (120, information not present in the schema), and states the boolean return shape ('paid true or false'). It doesn't say what happens on timeout beyond returning false, or how frequently it polls, which keeps it off a 5.

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?

Two tight sentences, front-loaded with the blocking condition and the constraint, with the return value appended last. The parenthetical timeout detail is dense but earns its place; nothing reads as filler.

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 4-parameter blocking/polling tool with no annotations and no output schema, the description covers waiting behavior, defaults, and return value, but leaves `confirmations` and the address-targeting question unaddressed. An agent could still call it, but would be guessing on two of four inputs.

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 only 25%, so the description must compensate and it only partly does: it clarifies `timeout_seconds` (default 120, max 300) and loosely characterizes `amount` as a holding threshold, but `confirmations` is never mentioned and the semantics of the required `address` argument remain ambiguous against the 'this wallet's addresses' phrasing.

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 ('Waits until') and a specific condition ('one of this wallet's addresses holds an amount'), which clearly separates it from read-only siblings like north_balance or north_received. It's slightly muddled by saying 'one of this wallet's addresses' while the schema requires a single `address` argument, so an agent must infer whether the wait applies to the given address or the whole wallet.

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?

Waiting for funds implies its own use case (blocking poll until payment lands) and the timeout defaults make that context usable, but there is no explicit guidance on when to call this vs. polling north_balance or north_received. No alternatives or exclusion conditions are named.

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