Skip to main content
Glama
Sign In
KrakenMCP

KrakenMCP

by gateniomer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

run

Invoke a named tentacle to delegate planning, coding, review, or research to a headless coding agent, keeping code changes isolated until approved.

Instructions

Run any tentacle by name, including custom ones.

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": {
      "tentacle": "<tentacle>"
    },
    "name": "run"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoRepository path
agentNo
inputNo
modelNo
effortNo
plan_idNo
sessionNoRun group labeldefault
tentacleYes
context_runsNoFinished run ids to pass in as context

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.3

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it says nothing about whether running blocks, spawns background work, mutates state, consumes model quota, or what a run returns. 'Including custom ones' hints at an extensible registry but discloses no operational traits at all.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with no filler, front-loaded on the verb and resource. Its brevity is efficient but crosses into under-specification given the tool's parameter surface.

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 nine-parameter, multi-agent dispatch tool with no annotations and no output schema, one sentence is far too thin — an agent cannot tell how to select an agent/model, what session grouping does, or how context_runs affects the run. Complexity is high and the description covers only the required name.

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 only 33%, so the description must compensate for nine parameters, and it explains just one ('by name' → the required `tentacle`). The meaning of cwd, agent, input, model, effort, plan_id, session, and context_runs is left entirely undocumented.

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+resource ('Run any tentacle') and adds scope ('by name, including custom ones'), which tells an agent that a named tentacle must already exist. It does not differentiate from the highly overlapping siblings 'execute', 'chain', or 'resume', so the purpose is clear but not uniquely placed.

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 when-to-use or when-not-to-use guidance and no named alternative, despite 'execute', 'chain', 'resume', and 'plan' sitting in the same sibling set. The agent is left to infer that 'run' is the general dispatcher while the others are specialized paths.

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