Skip to main content
Glama
ddonathan

IT Glue MCP Server

by ddonathan

Create IT Glue Configuration

itglue_create_configuration

Create a new device or asset configuration in IT Glue to document IT infrastructure details like hostname, IP, serial number, and warranty information for an organization.

Instructions

Create a new configuration (device/asset) in IT Glue.

Args:

  • organization_id (number): Organization ID (required)

  • name (string): Configuration name (required)

  • configuration_type_id (number): Type ID

  • configuration_status_id (number): Status ID

  • hostname (string): Hostname

  • primary_ip (string): Primary IP address

  • mac_address (string): MAC address

  • serial_number (string): Serial number

  • asset_tag (string): Asset tag

  • manufacturer_id (number): Manufacturer ID

  • model_id (number): Model ID

  • operating_system_id (number): OS ID

  • notes (string): Notes

  • warranty_expires_at (string): Warranty expiration (YYYY-MM-DD)

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

Returns: The created configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organization_idYesOrganization ID (required)
nameYesConfiguration name (required)
configuration_type_idNoConfiguration type ID
configuration_status_idNoConfiguration status ID
hostnameNoHostname
primary_ipNoPrimary IP address
mac_addressNoMAC address
default_gatewayNoDefault gateway
serial_numberNoSerial number
asset_tagNoAsset tag
manufacturer_idNoManufacturer ID
model_idNoModel ID
operating_system_idNoOperating system ID
operating_system_notesNoOperating system notes
location_idNoLocation ID
contact_idNoContact ID
notesNoNotes
warranty_expires_atNoWarranty expiration date (YYYY-MM-DD)
installed_byNoInstalled by
purchased_byNoPurchased by
purchased_atNoPurchase date (YYYY-MM-DD)
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 already indicate this is a non-destructive write operation (readOnlyHint: false, destructiveHint: false), which the description doesn't contradict. The description adds minimal behavioral context by specifying it creates 'a new configuration' and mentions the return value, but doesn't cover important aspects like authentication requirements, rate limits, or what happens on duplicate entries. With annotations covering safety, this is adequate but not rich.

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

Conciseness3/5

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

The description is front-loaded with the core purpose, but the Args section is redundant with the schema and includes incomplete parameter information. The structure is clear but contains wasted space repeating schema details without adding value, making it less efficient than it could be.

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 22 parameters, no output schema, and annotations covering basic safety, the description is minimally adequate. It states the purpose and return value, but lacks guidance on usage, error handling, or detailed behavioral context. The high parameter count and mutation nature suggest more completeness would be beneficial, but annotations help bridge some 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 100%, so the schema fully documents all 22 parameters. The description lists only 16 parameters in its Args section, omitting several from the schema (e.g., default_gateway, location_id), and doesn't add any meaningful semantic context beyond what's already in the schema descriptions. This meets the baseline for high schema coverage.

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 the verb ('Create') and resource ('new configuration (device/asset) in IT Glue'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'itglue_create_contact' or 'itglue_create_flexible_asset' beyond the resource name, which is why it doesn't reach a perfect score.

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 organization_id from list_organizations), when to choose configuration vs flexible_asset, or any exclusions. The agent must infer usage from the tool name alone.

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