Skip to main content
Glama

north_faucet

Requests a first coin from a trusted faucet to a fresh wallet address after a small proof-of-work, enabling initial funding without exposing recovery words.

Instructions

Asks a faucet for a first coin, to a fresh address of this wallet. The wallet does a small piece of work for it first (hashing, usually some seconds, a few minutes at the most). Give the address of a faucet that the owner or a page you trust named. The coin is in the wallet with the next block.

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": {
      "url": "<url>"
    },
    "name": "north_faucet"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses an in-call proof-of-work cost ('some seconds, a few minutes at the most') and the resulting delay ('the coin is in the wallet with the next block'). It does not cover failure modes (bad/untrusted faucet, exhausted faucets) or what the call 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?

The purpose is front-loaded in the first sentence, with cost, trust requirement, and settlement timing following in a logical order. Four sentences is reasonable, with only slight verbosity in the opening clause.

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

Completeness4/5

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

For a one-parameter, no-annotation, no-output-schema tool, the definition covers purpose, latency/side effects, the trust constraint on the input, and when the result materializes. Missing only edge-case behavior on faucet failure.

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?

Schema coverage is 0% and the single 'url' parameter has no description in the schema, but the description compensates by explaining it is a faucet address and must come from the owner or a trusted page. This adds real meaning and a safety constraint beyond a bare string of maxLength 500.

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 names a specific action and resource: requesting a first coin from a faucet into the wallet's fresh address. It is clearly distinct from sibling tools like north_balance or north_pay, though the phrase 'to a fresh address of this wallet' is grammatically awkward.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: this is for obtaining the first coin, requires a faucet URL from the owner or a trusted page, and entails a short proof-of-work wait. No explicit when-not-to-use or alternative is given, so it falls short of a 5.

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