Skip to main content
Glama

update_location

Update an existing IT Glue location by providing only the fields to change. Modify address, contact details, or set as primary.

Instructions

Update an existing location in IT Glue. Only the fields you supply are changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe location ID to update
faxNoFax number
cityNoCity
nameNoLocation name/title
notesNoFree-text notes
phoneNoPhone number
primaryNoWhether this is the organization's primary location
address_1NoAddress line 1
address_2NoAddress line 2
region_idNoRegion/state ID
country_idNoCountry ID
postal_codeNoPostal/ZIP code
organization_idYesOrganization ID that owns the location
Behavior3/5

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

No annotations exist, so description carries full burden. It discloses partial update behavior, but lacks details on authorization, side effects, or return values.

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?

Two sentences, front-loaded with action, no fluff. Every word earns its place.

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?

Despite many parameters and siblings, description is minimal. Lacks return value info and usage context vs other location tools. Adequate but not comprehensive.

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 coverage is 100%, so description adds no new per-parameter info beyond schema. Baseline 3 is appropriate as description only provides overall context.

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 action (update) and resource (location in IT Glue), and distinguishes it from create_location by noting partial update behavior.

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

Usage Guidelines3/5

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

The description mentions only supplied fields change, which implies partial update, but does not explicitly state when to use this tool versus alternatives like create_location or delete_location.

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/wyre-technology/itglue-mcp'

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