Add a new individual or organization to Little Green Light CRM, capturing key details like name, email, phone, and address.
Create a new constituent in LGL
| Name | Required | Description | Default |
|---|---|---|---|
| zip | No | ||
| city | No | ||
| No | Primary email address | ||
| phone | No | Primary phone number | |
| state | No | ||
| street | No | ||
| last_name | No | ||
| first_name | No | ||
| constituent_type | No | individual | |
| organization_name | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description states 'Create' implying mutation, consistent with annotations (readOnlyHint=false). However, it lacks details on authentication requirements, success/failure behavior, or side effects beyond the creation action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence with no wasted words, but it is overly minimal. It could be expanded to include more context without sacrificing brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 10 optional parameters, no output schema, and many sibling tools, the description fails to adequately guide an AI agent. Important context about constituent creation (e.g., defaults, required fields for different constituent types) is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 10 parameters with only 20% description coverage. The description adds no meaning beyond the schema, leaving most parameters unexplained. No additional semantic information is provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Create a new constituent in LGL', identifying the verb, resource, and context. However, it does not differentiate from sibling tools like 'create_event' or 'create_relationship', which have similarly named purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 such as 'update_constituent' or 'search_constituents'. No prerequisites, exclusions, or context for usage are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/WillHeadlee/Little-Green-Light-MCP-Server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server