Skip to main content
Glama
ddonathan

IT Glue MCP Server

by ddonathan

Create IT Glue Password

itglue_create_password

Create a new password entry in IT Glue by specifying organization, name, credentials, and optional details like URL or notes for secure documentation.

Instructions

Create a new password entry in IT Glue.

Args:

  • organization_id (number): Organization ID (required)

  • name (string): Password entry name (required)

  • password_category_id (number): Category ID

  • username (string): Username

  • password (string): Password value

  • url (string): Associated URL

  • notes (string): Notes

  • password_folder_id (number): Folder ID

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

Returns: The created password entry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organization_idYesOrganization ID (required)
nameYesPassword entry name (required)
password_category_idNoPassword category ID
usernameNoUsername
passwordNoPassword value
urlNoURL associated with this password
notesNoNotes
password_folder_idNoPassword folder ID
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-readOnly, non-destructive, non-idempotent, open-world operation. The description adds minimal behavioral context beyond this, only noting it 'Returns: The created password entry.' It doesn't disclose authentication requirements, rate limits, or error conditions, but doesn't contradict annotations.

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 with a clear purpose statement followed by a parameter list. However, the 'Args' section is redundant given the schema, and the structure could be more front-loaded with critical usage information rather than parameter details already covered elsewhere.

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 no output schema, the description adequately covers the basic purpose but lacks important context. It doesn't explain what the return value contains, error handling, or how this tool relates to siblings. Given the annotations provide safety information, this is minimally complete but could be more informative.

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?

With 100% schema description coverage, the input schema already documents all parameters thoroughly. The description's 'Args' section merely repeats what's in the schema without adding meaningful context about parameter relationships, constraints, or examples. 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.

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 password entry') and resource ('in IT Glue'), distinguishing it from sibling tools like itglue_get_password or itglue_list_passwords. It explicitly identifies the tool's function without being tautological.

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 itglue_update_password or itglue_check_password_access. It lacks context about prerequisites, appropriate scenarios, or exclusions, leaving the agent without usage direction.

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