Little Green Light MCP Server

create_contact_report

Log a contact report for a constituent by providing text, subject, date, and contact type.

Instructions

Create a new contact report nested under a constituent

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": {
      "constituent_id": "<constituent_id>",
      "text": "<text>"
    },
    "name": "create_contact_report"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	Content of report
`subject`	No
`contact_date`	No	YYYY-MM-DD
`contact_type`	No	e.g. Phone, In Person, Email
`constituent_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.0Jul 29, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already indicate a non-read-only mutation. The description adds minimal behavioral context beyond nesting. No contradictions.

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?

Single sentence, no fluff. Could add more value without sacrificing conciseness.

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?

Lacks context about side effects, defaults, output, or behavior for optional parameters. Insufficient for a mutation with 5 parameters.

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?

Schema coverage is 60% but description does not explain parameters beyond schema. Subject and constituent_id lack schema descriptions and are not covered in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states action (create), resource (contact report), and context (nested under a constituent). It distinguishes from sibling CRUD operations on contact reports.

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?

No guidance on when to use this tool versus alternatives like create_note. Lacks explicit when/when-not or prerequisites.

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

Deploy Server