nibgate

get_ledger

Get the public Nibgate activity ledger: recent views, unlocks, payments, tips (including funded pending holds marked status=held), onchain ratings, and privacy-safe nibshare views/unlocks (titles, wallets, amounts, tx — never the private share link) across verified sites. Held tips are pending and do not count toward completed-tip totals; refunds appear as negative tip entries. Use GET /hub/tips/held?domain={domain} to check pending tips for any exact domain, including external sites. Includes wallet addresses, tx hashes, and receipts where available.

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

Input Schema

Name	Required	Description
`skip`	No	Pagination offset.
`type`	No	Filter by activity type.
`limit`	No	Max results (default 20).
`domain`	No	Filter by site domain, e.g. example.nibgate.xyz.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 7, 2026

addedInput schema / properties / domain

Added value: +{
+  "description": "Filter by site domain, e.g. example.nibgate.xyz.",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Max results (default 20).",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / skip

Added value: +{
+  "description": "Pagination offset.",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / type

Added value: +{
+  "description": "Filter by activity type.",
+  "enum": [
+    "views",
+    "unlocks",
+    "payments",
+    "ratings",
+    "tips",
+    "nibshare"
+  ],
+  "type": "string"
+}

Changed4 schema fields changedNov 7, 2026

removedInput schema / properties / domain

Removed value: -{
-  "description": "Filter by site domain, e.g. example.nibgate.xyz.",
-  "type": "string"
-}

removedInput schema / properties / limit

Removed value: -{
-  "description": "Max results (default 20).",
-  "maximum": 100,
-  "minimum": 1,
-  "type": "integer"
-}

removedInput schema / properties / skip

Removed value: -{
-  "description": "Pagination offset.",
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / type

Removed value: -{
-  "description": "Filter by activity type.",
-  "enum": [
-    "views",
-    "unlocks",
-    "payments",
-    "ratings",
-    "tips",
-    "nibshare"
-  ],
-  "type": "string"
-}

Changed1 schema field changedSep 30, 2026

changedInput schema / properties / type / enum

Previous value: -[
-  "views",
-  "unlocks",
-  "payments",
-  "ratings"
-]New value: +[
+  "views",
+  "unlocks",
+  "payments",
+  "ratings",
+  "tips",
+  "nibshare"
+]

First observedSep 1, 2026

TDQS

A3.7/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 disclose real behavior: held tips are pending and excluded from completed-tip totals, refunds surface as negative tip entries, and nibshare data is redacted to never expose the private share link. It omits auth/permission requirements and ordering/pagination behavior, keeping it short of 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?

Front-loads the resource and keeps to three dense sentences covering scope, tip semantics, and returned fields. The raw 'GET /hub/tips/held' reference is a slight distraction in an agent-facing description, but little is wasted.

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?

No output schema exists, and the description compensates by naming returned fields (titles, wallets, amounts, tx hashes, receipts). It does not describe result ordering or the shape of paginated responses, leaving a modest gap.

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 100%, so the schema already explains skip, type, limit, and domain; baseline is 3. The description adds context about what the ledger surfaces but gives no extra semantics for filter/pagination parameters.

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 ('Get') and resource ('public Nibgate activity ledger') and enumerates the included activities (views, unlocks, payments, tips, ratings, nibshare), which separates it from get_platform_stats and get_leaderboards without naming them. Sibling differentiation is implied by content coverage rather than stated explicitly.

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?

No explicit statement of when to choose this tool over explore_content, get_leaderboards, or get_platform_stats. The only routing guidance points at a raw HTTP endpoint ('Use GET /hub/tips/held?domain={domain}') rather than a sibling MCP tool, so usage is only loosely implied.

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

All nibgate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.