GoClaw MCP Server

goclaw_agent_links_set

Create or update delegation links between AI agents to define task handoffs and responsibilities within the GoClaw gateway infrastructure.

Instructions

Create or update a delegation link between agents

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": {
      "agent_id": "<agent_id>",
      "target_agent_id": "<target_agent_id>",
      "description": "<description>"
    },
    "name": "goclaw_agent_links_set"
  }
}

Input Schema

Name	Required	Description
`agent_id`	Yes	Source agent ID
`target_agent_id`	Yes	Target agent ID to delegate to
`description`	Yes	Description of what is delegated

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Create or update') but doesn't clarify whether this is idempotent, what permissions are required, whether it's destructive, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that states the core purpose without any wasted words. It's appropriately sized for a tool with three parameters and no complex behavioral nuances to explain.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'delegation link' entails in this system, what the response looks like, error conditions, or side effects. Given the complexity implied by sibling tools and lack of structured data, more context is needed.

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 description coverage is 100%, so the schema already documents all three parameters adequately. The description doesn't add any additional semantic context about the parameters beyond what's in the schema (e.g., format of agent IDs, examples of descriptions). This meets the baseline for high schema coverage.

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 clearly states the action ('Create or update') and resource ('delegation link between agents'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'goclaw_agent_links_remove' or 'goclaw_agent_links_list' beyond the verb difference, which prevents a perfect score.

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 description provides no guidance on when to use this tool versus alternatives like 'goclaw_agent_links_remove' or 'goclaw_agent_links_list'. It doesn't mention prerequisites, consequences, or typical use cases, leaving the agent with minimal context for decision-making.

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

Deploy Server