Skip to main content
Glama

List Connections

connections.list
Read-onlyIdempotent

Retrieve connections for a Maya node with direction and type filters. Limits response to 500 connections by default.

Instructions

List connections on a Maya node with direction and type filters. Returns max 500 connections by default to limit response size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYesNode name to query connections for
limitNoMax connections to return (default 500, use 0 for unlimited)
directionNoFilter by direction: incoming, outgoing, or bothboth
connections_typeNoFilter by connection type (e.g., 'animCurve', 'shader')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYes
countYes
errorsYes
truncatedNo
connectionsYes
total_countNo
_size_warningNo
_original_sizeNo
_truncated_sizeNo
Behavior4/5

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

The description adds value beyond annotations by specifying the default limit of 500 connections to limit response size, which is useful behavioral information.

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?

Single sentence, front-loaded with core purpose, no unnecessary words.

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?

Covers essential aspects: node parameter, filters, and limit. Output schema exists so return format is covered elsewhere.

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% with parameter descriptions. The description only generically mentions 'direction and type filters', adding no meaningful extra 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 tool lists connections on a Maya node with direction and type filters, distinguishing it from sibling tools like connections.connect, connections.disconnect, etc.

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 implies usage for listing connections but does not explicitly state when to use this tool over alternatives like connections.get or connections.history.

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/GimbalGoats/GG_MayaMCP'

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