Skip to main content
Glama
ddonathan

IT Glue MCP Server

by ddonathan

Update IT Glue Location

itglue_update_location
Idempotent

Modify location details in IT Glue to update address, contact information, or primary status for managed service provider records.

Instructions

Update an existing location in IT Glue.

Args:

  • id (string|number): Location ID (required)

  • name (string): Location name

  • primary (boolean): Is this the primary location

  • address_1 (string|null): Address line 1

  • address_2 (string|null): Address line 2

  • city (string|null): City

  • postal_code (string|null): Postal/ZIP code

  • region_id (number|null): Region/state ID

  • country_id (number|null): Country ID

  • phone (string|null): Phone number

  • fax (string|null): Fax number

  • notes (string|null): Notes

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

Returns: The updated location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique ID of the resource
organization_idNoOrganization ID
nameNoLocation name
primaryNoIs this the primary location
address_1NoAddress line 1
address_2NoAddress line 2
cityNoCity
postal_codeNoPostal/ZIP code
region_idNoRegion ID (state/province)
country_idNoCountry ID
phoneNoPhone number
faxNoFax number
notesNoNotes
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 cover key behavioral traits (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), so the description doesn't need to repeat these. It adds minimal context by specifying it updates an 'existing' location and mentions the return value, but doesn't elaborate on side effects, permissions, or error conditions beyond what annotations imply.

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 appropriately sized and front-loaded with the core purpose. The parameter listing is somewhat redundant given the schema, but it's organized clearly. The return statement is concise. Overall, it's efficient with minimal fluff.

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?

Given the tool's complexity (14 parameters, mutation operation) and rich annotations, the description is adequate but lacks depth. It doesn't explain output details (no output schema provided), error handling, or integration with sibling tools. It meets minimum requirements but doesn't fully compensate for the absence of an output schema.

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 parameters are fully documented in the schema. The description lists parameters but adds no meaningful semantics beyond the schema (e.g., it doesn't explain relationships between fields like region_id and country_id). With high schema coverage, the baseline is 3, and the description doesn't significantly enhance understanding.

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 action ('Update') and resource ('existing location in IT Glue'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'itglue_create_location' by specifying it's for updates, though it doesn't explicitly differentiate from other update tools like 'itglue_update_contact'.

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 location ID), when not to use it, or how it compares to similar update tools for other resources like contacts or organizations in the sibling list.

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