Skip to main content
Glama

add_contact_note

Idempotent

Add an internal note to a contact in the approved business. Reuse the same request ID on retry.

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>",
      "body": "<body>",
      "requestId": "<requestId>"
    },
    "name": "add_contact_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bodyYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. Beyond them, the description adds meaningful context: the note is 'internal', so it is not customer-visible, and it gives the concrete retry rule of reusing the same request ID. It does not describe what is returned or what happens on validation failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler, and the core action is front-loaded ahead of the retry caveat. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple three-parameter mutation with annotations covering safety and idempotency, and no output schema is needed. However, the description omits what the call returns and does not compensate for the zero schema coverage on body and id limits. Adequate, but with clear gaps.

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

Parameters3/5

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

Schema description coverage is 0%, so the schema alone leaves parameters unexplained. The description does clarify the least obvious one, requestId, as an idempotent retry key, and its framing ('note to a contact') maps id to a contact identifier and body to the note text. Still, nothing is said about format constraints such as the 4,000-character body limit or the id pattern.

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 states a specific verb and resource: 'Add an internal note to a contact.' That is clearly distinct from sibling tools such as add_contact_tag or update_contact_profile. The qualifier 'in the approved business' adds a scope constraint, but no explicit sibling differentiation is offered.

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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The retry instruction ('Reuse the same request ID on retry') is operational, not when-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources