Skip to main content
Glama
Sign In
Hystersis MCP Server

Hystersis MCP Server

by Himan-D
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

create_relation

Create a typed relationship between two entities in the Hystersis knowledge graph to link data with a specified relation type.

Instructions

Create a relationship between two entities in the Hystersis knowledge graph.

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>",
      "relation_type": "<relation_type>"
    },
    "name": "create_relation"
  }
}

Input Schema

NameRequiredDescriptionDefault
from_entityYesSource entity ID or name
to_entityYesTarget entity ID or name
relation_typeYesRelationship type (e.g., 'USES', 'KNOWS', 'DEPENDS_ON')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided. Description does not disclose side effects, idempotency, permissions, or error cases (e.g., duplicate relationship). Mutation tool needs more behavioral context.

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, no extraneous words, clearly communicates the tool's core action.

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?

Adequate for a simple create operation with clear parameters, but lacks usage guidelines and behavioral notes. Could be improved with idempotency or prerequisite info.

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 covers all 3 parameters with descriptions (source entity, target entity, relation type). Description adds no extra param info beyond schema. Baseline 3 as schema coverage is 100%.

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?

Clearly states verb 'Create', resource 'relationship between two entities', and context 'Hystersis knowledge graph'. Differentiates from sibling create_entity which creates entities, not relationships.

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 explicit guidance on when to use this tool vs alternatives. Implies usage for connecting entities, but no exclusions or when-not-to-use.

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