Skip to main content
Glama
WillHeadlee

Little Green Light MCP Server

by WillHeadlee

update_group_membership

Idempotent

Update an existing group membership record in Little Green Light CRM by specifying the record ID and optionally changing the group. Keeps constituent-group associations current.

Instructions

Update a group membership record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
group_idNo
Behavior2/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. Description adds no behavioral context such as what fields are updated, side effects, or required permissions.

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?

Single sentence is concise but lacks structure. No front-loading of key info; it's just a minimal statement.

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?

No output schema, low schema coverage, many similar sibling tools. Description does not specify updateable fields, response, or effect of group_id. Incomplete for effective tool use.

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

Parameters1/5

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

Schema has 2 parameters with 0% coverage in description. No explanation of id or group_id meaning, format, or usage. Description provides zero insight beyond schema.

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?

Description clearly states verb 'Update' and resource 'group membership record'. It distinguishes from related siblings like create_membership, delete_membership, but not clearly from update_membership. Still, purpose is unambiguous.

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_membership or add_constituent_to_group. No context about prerequisites or when-not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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