Skip to main content
Glama

Get the IC donation total + donor wall (public)

ic_donations_total
Read-only

Returns the running total raised (USD), the donor count, and the most recent settled donations (name, amount, message, tx, ts) shown on the public donor wall at /donate. No auth required. Args: { limit?: number (1-50, default 10) }.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent donations to return (1-50, default 10).

Output Schema

NameRequiredDescriptionDefault
okNotrue when the call did what it was asked; false with `error` and `error_kind` when it did not
textNoThe tool's reply when it returns plain text instead of JSON
errorNoWhy the call failed, in a sentence a person can act on. Present only when ok is false.
resultNoThe tool's value when it returns a list or a single value instead of an object
error_kindNoMachine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "The tool's JSON result. Every field the tool's description names is present at the top level; ok, error and error_kind follow the shared envelope.",
      +  "properties": {
      +    "error": {
      +      "description": "Why the call failed, in a sentence a person can act on. Present only when ok is false."
      +    },
      +    "error_kind": {
      +      "description": "Machine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient"
      +    },
      +    "ok": {
      +      "description": "true when the call did what it was asked; false with `error` and `error_kind` when it did not"
      +    },
      +    "result": {
      +      "description": "The tool's value when it returns a list or a single value instead of an object"
      +    },
      +    "text": {
      +      "description": "The tool's reply when it returns plain text instead of JSON"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many recent donations to return (1-50, default 10)."
  3. Changed1 schema field changed
    • removedInput schema / properties / limit / description
      Removed value: -"How many recent donations to return (1-50, default 10)."
  4. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many recent donations to return (1-50, default 10)."
  5. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description still adds real behavior: no authentication needed, data is publicly exposed, and only 'settled' donations appear on the wall (implying pending ones are omitted). It does not describe rate limits or how fresh the 'running total' is.

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?

Content is front-loaded: returns, then no-auth, then arguments, in three compact clauses. Minor waste comes from restating the limit range and default that the schema already declares.

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?

With a single optional parameter, full schema coverage, annotations, and an output schema, the description supplies what structure cannot: public/no-auth access and the 'settled only' filter. Only minor gaps remain, such as ordering of 'most recent' donations and whether the total is cached.

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% and the single optional parameter is fully documented in the schema, so the baseline is 3. The description's 'Args: { limit?: number (1-50, default 10) }' merely repeats the schema verbatim rather than adding meaning such as ordering of the returned donations.

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 verb (returns) and enumerates the exact resources returned: running USD total, donor count, and recent settled donations with their fields. It also anchors the tool to the public donor wall at /donate. It never explicitly contrasts with the sibling ic_donate, so an agent must infer that this is the read-side view rather than a donation action.

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?

The phrase 'shown on the public donor wall' and 'No auth required' imply the retrieval context, but there is no explicit when-to-use or when-not-to-use statement, and no named alternative (e.g., ic_donate for making a donation). Usage is derivable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.