Skip to main content
Glama
Sign In
Kremis

Kremis

by TyKolt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

kremis_retract

Decrement the weight of an edge between two entities to invalidate or retract a previously registered signal in the knowledge graph.

Instructions

Decrement the weight of an edge between two entities (edge invalidation / signal retraction)

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": {
      "from_entity": "<from_entity>",
      "to_entity": "<to_entity>"
    },
    "name": "kremis_retract"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_entityYesTarget entity ID (the edge destination)
from_entityYesSource entity ID (the edge origin)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.18.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist; description lacks detail on side effects (e.g., decrement amount, behavior if edge missing or weight zero), idempotency, or required permissions.

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?

Single sentence with no wasted words; purpose is front-loaded and immediately clear.

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?

Lacks return value description, error conditions, and edge cases (e.g., what happens when weight reaches zero). More context needed for a mutation tool with no annotations.

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 already describes both parameters clearly (source/target entity IDs). Description adds context of edge invalidation but no additional parameter-level detail, meeting baseline.

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 decrements edge weight for invalidation/retraction, specific verb+resource, and distinguishes from sibling tools like kremis_ingest (add) and kremis_lookup (read).

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 usage guidelines provided; no mention of when to use this tool vs alternatives (e.g., deletion) or conditions like edge existence.

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