Little Green Light MCP Server

top_donors

Read-only

Retrieve top donors sorted by total giving amount. Filter by date range to analyze contributions within specific periods.

Instructions

Get top donors ranked by total giving, optionally within a date range

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

Input Schema

Name	Required	Description
`limit`	No
`end_date`	No	YYYY-MM-DD
`start_date`	No	YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.0Jul 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds minimal behavioral insight beyond what annotations provide (e.g., no mention of pagination, limit interpretation, or ordering direction).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no filler words, clearly structured with verb and optional filter.

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?

No output schema; description implies a list of donors with total giving but omits ordering direction (descending) and return fields. Adequate given the tool's simplicity and annotations.

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?

The schema covers 67% of parameters with descriptions (dates). The description adds context: limit filters the number of donors, and date range is optional. This compensates for the missing schema description on 'limit'.

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 clearly states the verb 'Get', the resource 'top donors', and the ranking method 'by total giving' with optional date range. It is specific and distinct from sibling tools which are mostly CRUD operations.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives like 'recent_donors' or 'lapsed_donors'. It only mentions the optional date range but no context on when it's appropriate to use.

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

Deploy Server