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

Little Green Light MCP Server

by WillHeadlee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

update_phone_number

Idempotent

Update a constituent's phone number record in Little Green Light by providing the phone ID and optionally updating the number, primary status, or phone type.

Instructions

Update an existing phone number record by Phone ID

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": {
      "id": "<id>"
    },
    "name": "update_phone_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPhone ID
numberNo
is_primaryNo
phone_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already indicate it's an update (non-readOnly, non-destructive, idempotent). The description adds no additional behavioral context, such as what happens if the ID doesn't exist or permissions required.

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?

The description is a single, concise sentence that front-loads the core purpose. Slightly more detail could be added without losing 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?

As a mutation tool with 4 parameters and no output schema, the description is too minimal. It fails to mention optional fields or any constraints, leaving gaps for agent understanding.

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?

With only 25% schema description coverage, the description should compensate but only mentions the 'id' parameter. No details on 'number', 'is_primary', or 'phone_type' formats or constraints.

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?

The description clearly states the action ('Update'), the resource ('existing phone number record'), and the identifier ('by Phone ID'). It effectively distinguishes from create_phone_number and delete_phone_number.

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 is provided on when to use this tool versus alternatives like update_email_address. There are no prerequisites or exclusions mentioned.

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