Skip to main content
Glama
Sign In
Little Green Light MCP Server

Little Green Light MCP Server

by WillHeadlee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_contact_reports

Read-only

Retrieve contact reports from your Little Green Light CRM database. Optionally filter by constituent to focus on a donor's history.

Instructions

List contact reports, optionally filtered by constituent, or fetch all

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

Input Schema

NameRequiredDescriptionDefault
limitNo
constituent_idNoFilter by constituent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly and openWorld hints, so the description adds minimal behavioral context beyond 'or fetch all'. It does not contradict annotations, but fails to mention pagination or limit behavior.

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

Conciseness3/5

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

The description is concise and front-loaded, but omits important parameter semantics for 'limit'. It is not verbose, but could be improved with a brief note on limit's role.

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

Completeness2/5

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

Given no output schema and incomplete parameter documentation, the description lacks information on return format, ordering, or pagination. For a tool with siblings that offer more specific capabilities, it feels incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one of two parameters has a schema description (constituent_id). The description adds 'optionally filtered by constituent' but does not explain the 'limit' parameter, leaving its purpose unclear for the agent.

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 action ('list'), resource ('contact reports'), and optional filtering by constituent. It distinguishes from sibling 'get_contact_report' and hints at comparison with 'search_contact_reports' via simplicity, but does not explicitly contrast.

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 description implies usage for simple listing with optional filter or fetching all, but lacks explicit guidance on when to prefer this over the more advanced 'search_contact_reports' sibling.

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

Deploy Server

Other Tools