Skip to main content
Glama

north_pay

Pays NORTH to an address within owner-defined spending limits; use dry_run to preview the fee without signing or sending, and check state for 'handed' or 'in_block' confirmation.

Instructions

Pays an amount of NORTH to an address, within the owner's limits. With dry_run true nothing is signed or sent and the fee is shown. Read the state in the answer: only "handed" and "in_block" mean that the payment is on its way.

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_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNo
amountYesNORTH, as text, for example "1.5"
addressYes
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that dry_run signs and sends nothing and that only "handed" and "in_block" states mean the payment is in flight, but it omits irreversibility, whether retries duplicate a payment, and what the limit rejection looks like.

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?

Three tight sentences, front-loaded with the action, then the safety mode, then the result interpretation. The phrase "Read the state in the answer" is slightly oblique but no sentence is 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 value-transferring mutation with no annotations and no output schema, the definition covers simulation and partial state semantics but never enumerates the possible states or says what an agent should do on any other value, leaving a gap in the highest-risk area.

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 only 25%, so the description must compensate. It gives meaning to dry_run (simulation plus fee display) and to amount as NORTH, but leaves address and especially memo (200-char limit) completely undefined in both schema and prose.

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?

States a specific verb and resource: pays an amount of NORTH to an address, scoped by owner limits. That is enough to separate it from read-only siblings like north_balance or north_history, though it never names an alternative transfer route (e.g. north_faucet) to contrast with.

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?

It explains how to use the dry_run flag safely (nothing signed or sent, fee returned), which is real usage guidance, but it never says when an agent should prefer this tool over siblings or what preconditions must hold before a live payment.

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