Skip to main content
Glama

get_relationships

Retrieve relationships between assets with optional filters for type, source, and target. Use to analyze attack paths and asset connections in security audits.

Instructions

    Get relationships between assets with optional filtering.

    Args:
        relationship_type: Filter by type (e.g., "CAN_ASSUME", "CAN_REACH", "MAY_ACCESS")
        source_name: Filter by source asset name
        target_name: Filter by target asset name
        max_relationships: Maximum number to return (default: 50)
        snapshot_id: Optional snapshot ID (default: latest)

    Returns:
        List of relationships with source, target, and type.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
relationship_typeNo
source_nameNo
target_nameNo
max_relationshipsNo
snapshot_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description discloses return format, default max_relationships=50, and snapshot default. It does not mention side effects or read-only nature, but is adequate.

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 a well-structured docstring with Args and Returns sections. It is concise but could be slightly tighter; still very readable.

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?

With an output schema present, the description covers essential return structure and parameter context. Missing exact relationship type enumeration, but overall complete.

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

Parameters5/5

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

Schema has 0% description coverage, so the description fully compensates by explaining each parameter's purpose, examples, and defaults, adding significant meaning.

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 retrieves relationships between assets with optional filtering, using specific verb and resource. It distinguishes from siblings like get_assets and get_findings.

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?

While the description explains parameters, it provides no guidance on when to use this tool vs alternatives such as check_access or get_attack_paths, which may overlap.

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/cyntrisec/cyntrisec-cli'

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