Skip to main content
Glama
Sign In
Kremis

Kremis

by TyKolt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

kremis_path

Find the strongest weighted path between two nodes in a deterministic local knowledge graph.

Instructions

Find the strongest weighted path between two nodes

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "kremis_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnding node ID
startYesStarting 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, and the description lacks disclosure of behavioral traits such as algorithm details (e.g., whether it handles cycles), complexity, or semantics of 'strongest' (max vs min weight).

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?

Extremely concise single sentence with no wasted words. However, it lacks structure such as examples or formatting, which could improve usability without significant bloat.

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?

Without an output schema, the description does not explain the return format (e.g., list of nodes, edges, or aggregated weight). Also missing context about graph properties like directed/undirected, making it incomplete for an agent to confidently use.

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 has 100% coverage with descriptions for both parameters, so baseline is 3. Description adds no additional meaning beyond the schema, but it does not introduce confusion.

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?

Description clearly states the tool finds a path between two nodes and specifies 'strongest weighted', indicating optimization. However, it does not differentiate from sibling tool kremis_traverse, which likely also deals with paths.

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 siblings like kremis_traverse or kremis_lookup. The description does not mention prerequisites, alternatives, or exclusions.

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