Skip to main content
Glama
ddonathan

IT Glue MCP Server

by ddonathan

Create IT Glue Contact

itglue_create_contact

Add new contacts to IT Glue by specifying organization, name, title, contact details, and notes for MSP documentation.

Instructions

Create a new contact in IT Glue.

Args:

  • organization_id (number): Organization ID (required)

  • first_name (string): First name (required)

  • last_name (string): Last name (required)

  • title (string): Job title

  • contact_type_id (number): Contact type ID

  • location_id (number): Location ID

  • important (boolean): Mark as important

  • notes (string): Notes

  • contact_emails (array): Email addresses

  • contact_phones (array): Phone numbers

  • response_format (string): 'markdown' or 'json'

Returns: The created contact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organization_idYesOrganization ID (required)
first_nameYesFirst name (required)
last_nameYesLast name (required)
titleNoJob title
contact_type_idNoContact type ID
location_idNoLocation ID
importantNoMark as important contact
notesNoNotes
contact_emailsNoContact email addresses
contact_phonesNoContact phone numbers
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior3/5

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

Annotations indicate this is a non-readOnly, non-destructive, non-idempotent, open-world operation. The description adds that it 'Returns: The created contact,' which provides useful output context beyond annotations. However, it lacks details on permissions, error conditions, or rate limits, leaving behavioral gaps despite the annotations covering basic safety.

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 front-loaded with the core purpose, followed by a structured Args section and a Returns note. It's appropriately sized, but the Args section repeats schema information without adding value, slightly reducing efficiency. Overall, it's well-structured with minimal waste.

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?

For a creation tool with 11 parameters, no output schema, and annotations covering basic traits, the description is adequate but incomplete. It specifies the return but lacks details on response structure, error handling, or dependencies (e.g., organization_id must exist). Given the complexity, more contextual information would be beneficial.

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 100%, so the schema fully documents all parameters. The description lists parameters but adds no additional meaning beyond the schema (e.g., explaining what 'contact_type_id' represents or how arrays are structured). This meets the baseline for high schema coverage but doesn't enhance parameter understanding.

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 specific action ('Create a new contact') and resource ('in IT Glue'), distinguishing it from sibling tools like itglue_get_contact, itglue_list_contacts, and itglue_update_contact. The verb 'Create' precisely indicates a write operation, making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing organization), exclusions (e.g., not for updating contacts), or refer to sibling tools like itglue_update_contact for modifications. Usage context is implied but not explicitly stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ddonathan/itglue-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server