Skip to main content
Glama

add_relationship

Create a new relationship between two entities by specifying source and target codes/types and a relation type, with optional validity dates and metadata.

Instructions

Add a new relationship between two 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": {
      "source_entity_type": "<source_entity_type>",
      "source_code": "<source_code>",
      "relation_type": "<relation_type>",
      "target_entity_type": "<target_entity_type>",
      "target_code": "<target_code>"
    },
    "name": "add_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
metadataNo
valid_toNo
valid_fromNo
source_codeYes
target_codeYes
relation_typeYes
source_entity_typeYes
target_entity_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false. The description adds no behavioral context beyond the verb 'add' — it does not explain duplicate handling, validation rules, permission requirements, or how the validity window and metadata fields affect the write.

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 single sentence is front-loaded and free of filler. However, its brevity is under-specification rather than true conciseness for a mutation tool with 8 parameters.

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?

An output schema exists, so return values need not be explained, but the description is still far too thin for a non-idempotent write with 5 required parameters and zero schema descriptions. It leaves the agent without enough information to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 parameters, so the description must compensate, but it only implies that source and target entities plus a relation type are involved. It says nothing about valid_from/valid_to, metadata, or the distinction between *_entity_type and *_code fields.

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 states a specific verb and resource: adding a new relationship between two entities. It is clear what the tool does, but it does not distinguish itself from siblings such as add_entity, add_entity_identifier, or confirm_binding.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer its role from the name alone.

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