Skip to main content
Glama

Link Team Entries

team_link_entries

Link two team entries with a defined relationship type to connect related project context; requires TEAM_DB_PATH.

Instructions

Create a relationship between two team entries. Requires TEAM_DB_PATH.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "team_link_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
relNo
fromNo
textNo
typeNo
to_idNo
from_idNo
messageNo
source_idNo
target_idNo
descriptionNo
to_entry_idNo
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.
from_entry_idNo
project_numberNo
relationship_typeNoreferences

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
messageNo
successNo
categoryNoError category (validation, query, connection, internal)
duplicateNoTrue if relationship already existed
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
relationshipNo
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv9.1.0
    • addedInput schema / properties / message
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / rel
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / source_id
      Added value: +{
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • addedInput schema / properties / target_id
      Added value: +{
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • addedInput schema / properties / text
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv9.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive write, and the description adds only the TEAM_DB_PATH prerequisite. It says nothing about duplicate-link behavior (which matters given idempotentHint=false), whether links are directional, or what happens when a referenced entry does not exist.

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?

Two short sentences with the action front-loaded and zero filler. The brevity is appropriate in form, though it is under-specification rather than deliberate economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema excuses explaining return values, but for a 16-parameter tool with no required fields and heavily overlapping aliases, the description leaves everything an agent needs for a correct call unaddressed.

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

Parameters1/5

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

Schema coverage is 6% across 16 parameters, and the description contributes nothing. Critically, it never disambiguates the four 'from' aliases (from, from_id, from_entry_id, source_id) or the four 'to' aliases, nor rel vs relationship_type vs type, leaving the agent to guess which fields to populate.

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?

States a specific verb and resource: 'Create a relationship between two team entries.' An agent knows the effect immediately. It does not name or differentiate itself from the near-identical sibling link_entries, so it stops short of a 5.

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?

The only guidance is an environment prerequisite ('Requires TEAM_DB_PATH'). There is no statement of when to use this versus link_entries, team_visualize_relationships, or team_update_entry, and no mention of the entry states that make linking valid.

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