Skip to main content
Glama
Sign In
Kremis

Kremis

by TyKolt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

kremis_traverse

Traverse a knowledge graph from a specified node to discover connected entities, with configurable depth and edge filtering.

Instructions

Traverse the graph from a node to discover connected entities

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": {
      "node_id": "<node_id>"
    },
    "name": "kremis_traverse"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoTraversal depth (default: 2, max: 10)
top_kNoReturn only the K highest-weight edges (optional)
node_idYesThe starting node ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.18.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behaviors. It lacks details on traversal direction (outgoing/incoming), cycle handling, result formatting, or performance implications. The minimal description 'discover connected entities' is vague.

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 single concise sentence (9 words) with no fluff. However, given the tool's complexity, a slightly more detailed description might be warranted, but it is still efficiently written.

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

Completeness2/5

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

The tool has 3 parameters, no output schema, and no annotations. The description fails to explain the return value, traversal algorithm behavior, or how depth and top_k interact. This leaves significant gaps for the agent.

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?

All parameters have descriptions in the input schema (100% coverage), so the description adds no extra semantics beyond the schema. The baseline of 3 is appropriate; no additional param context is provided.

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 uses a specific verb 'traverse' and identifies the resource 'graph from a node' and the outcome 'discover connected entities'. It clearly states the tool's function but does not differentiate from sibling tools like kremis_lookup or kremis_path.

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?

No guidance on when to use this tool versus alternatives. The description does not provide context on appropriate use cases or contrast with sibling tools.

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

Deploy Server

Other Tools