Skip to main content
Glama
Sign In
Engram

Engram

by staticroostermedia-arch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

mcp_engram_relate_batch

Batch create directional relations (concept_a -> concept_b with label) in a single request, reducing round-trips for relationship graphs like process requirements and handoff lineage.

Instructions

Batch create multiple directional relations (VSA OP_BIND edges as ZEDOS_RELATION). Reduces round-trips for gluing many at once (e.g. process requires, handoff lineage). Used in loader and lean wake batching.

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": {
      "relations": "<relations>"
    },
    "name": "mcp_engram_relate_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
relationsYesList of {concept_a, concept_b, label} to relate a->b with label

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0-beta.2

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description bears full burden. It discloses creating 'VSA OP_BIND edges as ZEDOS_RELATION' and mentions batch behavior, but lacks details on side effects, idempotency, error handling, or 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?

Two sentences front-load the core purpose ('Batch create...') followed by usage examples. No wasted words.

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?

The description covers function and use cases but omits output behavior (e.g., return values, success/failure indicators). Given the single parameter and no output schema, completeness is moderate.

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 coverage is 100% with descriptions for all properties. The description adds value by specifying the VSA OP_BIND and ZEDOS_RELATION context, going beyond the schema's 'List of {concept_a, concept_b, label} to relate a->b with label'.

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 'Batch create multiple directional relations', specifying the verb (create), resource (relations), and batch nature. It distinguishes from the sibling 'mcp_engram_relate' by emphasizing batch operation and reduced round-trips.

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 provides context for when to use: 'Reduces round-trips for gluing many at once (e.g. process requires, handoff lineage). Used in loader and lean wake batching.' It implies use for batch creation but does not explicitly state when not to use or mention the singular alternative.

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