Skip to main content
Glama
jamesdeane2

MCP IT Glue Server

by jamesdeane2

create_location

Create a location record for an existing IT Glue organization, specifying address, contact details, notes, and primary location status.

Instructions

Create a new location.

Args: organization_id: Organization ID (required) name: Location name (required) address_1: Street address line 1 address_2: Street address line 2 city: City name region_id: Region/state ID postal_code: Postal/ZIP code country_id: Country ID phone: Phone number fax: Fax number notes: Additional notes primary: Whether this is the primary location

Returns: JSON string with the created location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
faxNo
cityNo
nameYes
notesNo
phoneNo
primaryNo
address_1No
address_2No
region_idNo
country_idNo
postal_codeNo
organization_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits, but it only states the return format ('JSON string with the created location'). It does not explain the side effects of setting primary=true, whether permissions are required, or what happens on duplicate names. 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: a one-sentence purpose, an Args list, and a Returns line. Every sentence serves a purpose, and there is no filler. It is longer than average due to the 12 parameters, but each entry is necessary because the schema lacks descriptions.

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 tool with 12 parameters, no annotations, and an output schema, the description covers parameter meanings and the return type adequately. However, it omits important context such as how to obtain valid region_id/country_id values (e.g., via list_regions/list_countries), what happens when primary is set, and whether address fields have dependencies. This makes the tool usable but not fully self-explanatory.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden of parameter documentation. It lists all 12 parameters with brief explanations, adding most value for less obvious fields like 'primary: Whether this is the primary location' and 'region_id: Region/state ID'. However, many explanations are nearly tautological (e.g., 'city: City name'), and no constraints or formats are provided.

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 starts with 'Create a new location.', which is a clear verb-resource statement that distinguishes this tool from its siblings (list_locations, update_location, delete_location, etc.). However, it gives no further detail about what a location means in this domain beyond the parameter names, so it stops short of being fully explicit.

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 like update_location. It only lists arguments and a return type, leaving the agent to infer from the 'create' verb that this is for adding new locations. No prerequisites, exclusions, or alternative routing are mentioned.

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