Skip to main content
Glama

list_relationships

Read-onlyIdempotent

Lists an entity's relationships by entity type and code, with optional direction, to reveal incoming or outgoing graph connections.

Instructions

List relationships for an entity.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity_type": "<entity_type>",
      "code": "<code>"
    },
    "name": "list_relationships"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
directionNooutgoing
entity_typeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world behavior, so safety is covered; the description adds nothing beyond that. It does not say whether the traversal is one hop or recursive, whether results are paginated, or what happens when the entity has no relationships. An output schema exists, so return shape itself need not be described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short, front-loaded sentence with no filler — efficient but under-specified rather than concise. There is room for a clarifying clause without bloat.

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?

Annotations and an output schema carry much of the burden, so the tool is not opaque. Still, directionality and entity reference semantics are missing, which are exactly the details an agent needs to invoke this correctly.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, and the description compensates only vaguely via "for an entity" (implying entity_type + code). Critically, the `direction` parameter defaults to "outgoing" but the description never mentions directionality (incoming/outgoing/both) or the accepted values, leaving a behaviorally significant input entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource pair ("List relationships") is concrete, but "for an entity" is the only scope qualifier and it is never defined — no statement of what a relationship is, what entity types are valid, or how this differs from add_relationship or graph_search. An agent knows the general operation but not its boundaries.

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?

There is no guidance on when to call this versus alternatives such as graph_search, list_bindings, or list_entities, and no stated prerequisites. The agent must infer usage purely from the title-like sentence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.