Skip to main content
Glama
Sign In
KrakenMCP

KrakenMCP

by gateniomer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

status

Check a run's or chain's progress, metrics, and result, optionally waiting up to 55 seconds for completion and requesting only newer progress updates.

Instructions

A run's or chain's status, progress, metrics and result. Blocks up to wait_seconds while it is in progress (sends progress notifications when the client asks for them).

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": {
      "run_id": "<run_id>"
    },
    "name": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoFull result instead of an excerpt
sinceNoCursor from the previous status: only newer progress lines
run_idYesRun id or chain id
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.3

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the two most important behavioral traits: the call blocks up to wait_seconds while work is in progress, and it emits progress notifications when the client requests them. It omits read-only framing and error/failure behavior, but the surprising long-blocking semantics are surfaced.

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 tight sentences with the payload contents front-loaded and the blocking caveat second. The parenthetical about progress notifications is slightly awkward but earns its place.

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

Completeness4/5

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

There is no output schema, and the description does summarize what comes back (status, progress, metrics, result) plus the excerpt-vs-full distinction implied by the schema. It stops short of describing the structure of the returned result or pagination via the since cursor, which would help for a polling tool.

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

Parameters4/5

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

Schema coverage is 75%, and the single undocumented parameter, wait_seconds, is exactly the one the description explains as a blocking wait. That adds real meaning beyond the schema, though it says nothing about how wait_seconds interacts with since or full.

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 gives a specific resource and enumerates what is returned: status, progress, metrics and result for a run or chain. It is clear enough to distinguish polling from mutating siblings like cancel or resume, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: you call this to poll an in-progress run, and the blocking behavior for wait_seconds is described, which hints at the long-poll pattern. There is no explicit when-not-to-use guidance or pointer to siblings such as cancel or resume.

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