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

Little Green Light MCP Server

by WillHeadlee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

create_constituent_invitation

Add a constituent to an event by creating an invitation record, with optional status update.

Instructions

Add a constituent to an event (creates an invitation record)

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>",
      "event_id": "<event_id>"
    },
    "name": "create_constituent_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes
constituent_idYes
invitation_statusNoe.g. Invited, RSVP, Attended

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations indicate this is a write operation (readOnlyHint=false) and not destructive. Description confirms creation but adds no additional behavioral details like idempotency or side effects.

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?

One clear sentence with no superfluous text. While brief, it efficiently conveys the core action.

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?

Minimal description for a tool with 3 parameters and no output schema. Lacks information about return value, default behavior, or relationship to invitations.

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 three parameters (invitation_status) has a description in the schema. The tool description does not elaborate on event_id or constituent_id, nor explains valid values for invitation_status. Schema coverage is low (33%), so description should compensate, but it does not.

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 ('Add a constituent to an event') and the resource (creates an invitation record). It distinguishes from siblings like 'create_event_invitation' by emphasizing the constituent perspective.

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 vs alternatives like update_invitation or delete_invitation. Lacks context on prerequisites or when not to use it.

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