Skip to main content
Glama

OpsRev Roofing AI

Create an AccuLynx contact

acculynx_create_contact

Create a contact with the supplied name and company contact types. Use List AccuLynx contact types for the IDs. Confirm the details with the user before creating.

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": {
      "firstName": "<firstName>",
      "lastName": "<lastName>",
      "contactTypeIds": "<contactTypeIds>"
    },
    "name": "acculynx_create_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
phoneNo
lastNameYes
emailTypeNo
firstNameYes
phoneTypeNo
companyNameNo
contactTypeIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already disclose readOnly=false, destructive=false, idempotent=false and openWorld=true, so the safety profile is covered. The description contributes the human-confirmation requirement, which is real added context, but says nothing about duplicate detection, error behavior, or what a successful create returns. That is a moderate gap for a non-idempotent write with open-world side effects.

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?

Three short sentences, front-loaded with the action, then the dependency, then the safety gate. No filler and nothing repeated from the title.

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?

For a non-idempotent create with 8 parameters, no output schema and no per-field schema descriptions, the description omits duplicate handling, required-field guidance beyond the implicit, response contents, and field-type conventions. It covers the ID source and confirmation step but leaves too much of a mutation call undefined.

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?

Schema description coverage is 0% across 8 parameters, so the description must carry the explanatory load. It only gestures at 'name' and 'company contact types'; the email, phone, emailType, phoneType, companyName and contactTypeIds GUID format (plus which three fields are required) are left entirely to the raw 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 opens with a specific verb and resource: 'Create a contact', and notes it takes a name plus company contact types. That is enough to separate it from acculynx_get_contact and acculynx_add_contact_note, though it never explicitly names or rules out the sibling create tools.

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

Usage Guidelines4/5

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

'Use List AccuLynx contact types for the IDs' gives a concrete prerequisite and points to the correct sibling for the dependency, and 'Confirm the details with the user before creating' supplies a workflow gate. It stops short of saying when not to create (e.g., an existing contact or a different CRM's create tool), so it is clear context without exclusions.

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