Skip to main content
Glama
ddonathan

IT Glue MCP Server

by ddonathan

List IT Glue Flexible Assets

itglue_list_flexible_assets
Read-onlyIdempotent

Retrieve custom documentation records from IT Glue, such as network diagrams, application runbooks, or vendor information, with options to filter by organization, asset type, name, or archived status.

Instructions

List flexible assets in IT Glue with optional filtering.

Flexible assets are custom documentation types defined by flexible asset types. Examples: Network documentation, Application runbooks, Vendor info, etc.

Args:

  • page (number): Page number (default: 1)

  • page_size (number): Items per page (default: 50)

  • organization_id (number): Filter by organization

  • flexible_asset_type_id (number): Filter by asset type (recommended)

  • name (string): Filter by name

  • archived (boolean): Filter by archived status

  • sort (string): Sort field

  • include (array): Related resources to include

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

Returns: List of flexible assets with their trait values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-indexed)
page_sizeNoNumber of items per page (max 1000)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
organization_idNoFilter by organization ID
flexible_asset_type_idNoFilter by flexible asset type ID (required for filtering by traits)
nameNoFilter by name (partial match supported)
archivedNoFilter by archived status
sortNoField to sort byname
sort_directionNoSort direction: asc (ascending) or desc (descending)asc
includeNoRelated resources to include
Behavior4/5

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

Annotations already provide strong behavioral hints (readOnly, openWorld, idempotent, non-destructive). The description adds valuable context beyond annotations: it explains what flexible assets are with concrete examples, mentions pagination behavior through the 'page' and 'page_size' parameters, and describes the return format options. This provides useful operational context that annotations don't cover.

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 with a clear purpose statement upfront, followed by explanatory context about flexible assets, then a parameter summary, and finally return information. It's appropriately sized for a tool with 10 parameters. Minor improvements could include better integration of the parameter information rather than a separate 'Args' section that duplicates schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (10 parameters, no output schema), the description provides good contextual completeness. It explains what flexible assets are, covers the main filtering capabilities, mentions pagination, and describes return format options. The annotations provide excellent behavioral coverage. The main gap is lack of explicit sibling tool differentiation, but overall it's quite complete for a list operation.

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 10 parameters thoroughly. The description's 'Args' section mostly repeats what's in the schema, adding minimal additional semantic context. It does add the note that flexible_asset_type_id is 'recommended' for trait filtering, which provides some guidance. The baseline of 3 is appropriate when schema coverage is complete.

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 tool's purpose: 'List flexible assets in IT Glue with optional filtering.' It specifies the verb ('List') and resource ('flexible assets'), and provides examples of what flexible assets are. However, it doesn't explicitly differentiate from sibling tools like 'itglue_get_flexible_asset' (singular) or 'itglue_list_flexible_asset_types', which would be needed for a score of 5.

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 provides implied usage context by mentioning 'optional filtering' and examples of flexible assets, but lacks explicit guidance on when to use this tool versus alternatives. It doesn't mention when to use this list tool versus 'itglue_get_flexible_asset' for single assets or 'itglue_list_flexible_asset_types' for types, nor does it specify prerequisites or exclusions.

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