Skip to main content
Glama

Tribal: Explore Relationships

tribal_explore

Traverse relationships from a knowledge item to reveal supporting evidence, contradictions, derivation sources, or superseding claims. Understand context by controlling traversal direction and depth.

Instructions

Traverse the relationship graph from a specific knowledge item. Use this after tribal_discover to understand an item's context: what supports it, what contradicts it, what it was derived from, or what it supersedes.

Typical workflow:

  1. tribal_discover finds relevant items

  2. Pick an item with interesting standing (high support, or contradictions)

  3. tribal_explore to see the evidence, contradictions, or derivation chain

Direction controls traversal:

  • "inbound": What do others assert about this item? (supports, contradictions, what supersedes it)

  • "outbound": What does this item assert about others? (what it's derived from, what it supports)

  • "both": Full neighbourhood in all directions

Relation types:

  • "supports": Evidence that reinforces the item

  • "contradicts": Evidence that challenges the item

  • "supersedes": A newer item that replaces this one

  • "derived_from": Provenance. The input used to produce this item

Depth controls hops: depth 1 = direct relations, depth 2 = relations of relations. Higher depth gives more context but more results. Depth is capped at 3 to avoid mixing unrelated evidence across distant graph regions; use multiple targeted calls for deeper investigation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNoMaximum traversal hops from anchor. 1 = direct relations only.
directionNoTraversal direction relative to the anchor item.inbound
include_referencesNoReturn references attached to each item.
include_standingNoCompute standing for each returned item. Adds latency at depth > 1.
item_idYesThe anchor item to explore from. Typically obtained from a tribal_discover result.
limitNoMaximum total results across all depths. Closer relations are returned first.
relation_typesNoFilter to specific relation types. Omit to return all types.
session_trace_idNoTrace ID from a prior tribal_discover call. If provided, this explore is part of the same retrieval session. The returned trace_id will match. Use this to build coherent feedback across discover + explore workflows.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
anchorYes
anchor_standingYes
exactYesTrue if all reachable items within depth were returned. False if truncated by limit.
related_itemsYes
trace_idYesTrace ID. Pass to tribal_feedback if rating this session.
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses depth cap at 3, latency implications for include_standing at depth > 1, and ordering of results. It does not mention authentication or rate limits, but it adequately describes behavioral traits for a read-like operation.

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?

The description is well-structured with clear sections (overview, workflow, direction, relation types, depth). It is front-loaded with the main action, and each sentence adds necessary information without redundancy. No wasted words.

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

Completeness5/5

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

Given the tool's complexity (graph traversal, 8 parameters, sibling tools), the description is highly complete. It integrates the tool into a workflow, explains parameter trade-offs, and sets expectations for depth limits. An output schema exists, so return value details are not needed.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds significant value beyond the schema by explaining the workflow, providing definitions for direction and relation types, and cautioning about depth. This extra context justifies a 4.

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's purpose: 'Traverse the relationship graph from a specific knowledge item.' It distinguishes itself from siblings like tribal_discover by describing a typical workflow, and the description is specific about traversing relationships (supports, contradicts, etc.).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly recommends using this tool after tribal_discover and outlines a clear workflow: discover, pick an item, then explore. It explains parameters like direction and relation types, aiding decision-making. It lacks explicit 'when not to use' instructions but provides sufficient context.

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/tribal-memory/tribal'

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