Skip to main content
Glama
jamesdeane2

MCP IT Glue Server

by jamesdeane2

create_contact

Create a contact record in IT Glue by supplying organization ID, first and last name, and optional contact type, location, emails, and phone numbers.

Instructions

Create a new contact in IT Glue.

Args: organization_id: Organization ID (required) first_name: Contact first name (required) last_name: Contact last name (required) contact_type_id: Contact type ID location_id: Location ID title: Job title important: Whether this is an important contact notes: Additional notes contact_emails: List of email objects with 'value' and optional 'label_name', 'primary' contact_phones: List of phone objects with 'value' and optional 'label_name', 'primary', 'extension'

Returns: JSON string with the created contact

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNo
titleNo
importantNo
last_nameYes
first_nameYes
location_idNo
contact_emailsNo
contact_phonesNo
contact_type_idNo
organization_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior such as whether it is a safe operation, if it can be reverted, or if there are side effects. It mentions 'Returns: JSON string with the created contact', which gives some output context, but does not cover potential errors, idempotency, or required permissions. This is a significant gap for a mutation tool.

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 well-structured with a clear Args section listing parameters and a Returns section. It is concise but complete for what it covers. No wasted words, and it is reasonably sized for a 10-parameter tool.

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?

Given the tool's complexity (10 parameters, 3 required, no annotations, and low schema coverage), the description as it stands is minimal. It lists parameters but omits details on how nested objects should be structured, what the JSON output contains beyond 'created contact', and any prerequisites (e.g., organization must exist). It does not fully equip an agent to call it correctly.

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?

The description adds a brief description for each parameter (e.g., 'Contact first name (required)'), which adds meaning beyond the schema titles. However, the schema coverage is 0%, so the description must compensate for that, but it does not elaborate deeply on complex parameters like contact_emails whose object structure is unspecified in the schema. It provides basic semantics but not comprehensive guidance.

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 clearly states 'Create a new contact in IT Glue' with a specific verb and resource. It lists the parameters and expected return. While it doesn't explicitly distinguish from sibling tools like update_contact, the name and purpose are clear enough for basic understanding.

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 versus alternatives. It doesn't mention that this tool is for creating, not updating, or any prerequisites like requiring an organization to exist. The description only lists parameters without context for selection.

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