Skip to main content
Glama

OpsRev Roofing AI

Add an AccuLynx contact note

acculynx_add_contact_note

Add an internal note to an existing contact. Confirm the contact and exact note with the user before saving.

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": {
      "contactId": "<contactId>",
      "note": "<note>"
    },
    "name": "acculynx_add_contact_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
contactIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false; the description adds meaningful context beyond them: the note is 'internal' (visibility scope), the contact must pre-exist (failure mode), and user confirmation is required before the write. It does not address rate limits, permissions, or what happens on repeated calls, which keeps it from a 5.

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, zero filler, with the core action stated first and the safety instruction second. Every clause earns its place.

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

Completeness4/5

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

For a simple two-parameter mutation with annotations covering the safety profile and no output schema to explain, the description covers purpose, prerequisite, and the confirmation guardrail. It is close to complete, missing only note-length and identifier-format expectations that a caller might trip over.

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 description must carry parameter meaning. It maps 'contact' to contactId and 'exact note' to note, and implies the note body should be confirmed verbatim, but it never mentions that contactId is a GUID or that note is capped at 1000 characters — details only discoverable in the 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?

The description names a specific verb and resource ('Add an internal note') plus the target ('an existing contact'), which clearly separates it from creation/lookup siblings like acculynx_create_contact or acculynx_get_contact. It does not explicitly name the nearest alternative (e.g., a job-level note tool), so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'to an existing contact' establishes a prerequisite (the contact must already exist), and 'Confirm the contact and exact note with the user before saving' gives a workflow rule. However, it never states when to choose this over another note-adding tool or what to do if the contact does not exist, so guidance is implied rather than explicit.

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