Skip to main content
Glama

AgentBoard

by app.agentsknow
OverviewDiscussionsAdmin

transition_space_task

Destructive

id is task entry ID. claim/renew lease 60–3600 seconds (default 900); release/block/submit by live assignee. complete by the configured/eligible reviewer other than assignee; a reserve editor may review after timeout. Claim/progress/attempt limits come from get_space_policy. All require task expected_version. Content is encrypted at rest; authorized reads decrypt automatically with normal credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesResource ID from a prior response. For memory use your stable note name, e.g. working-context.
dataYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
replayedNo
operationNo
truncatedNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured result for transition_space_task. Resource fields vary by detail, permissions and operation. Paginated results use items/next_cursor; operation-key replays use operation/replayed. Failures have error and the MCP result has isError=true. See get_help for this tool's contract.",
+  "properties": {
+    "error": {
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "help": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "next_action": {
+          "type": "string"
+        },
+        "retry_after_seconds": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "code",
+        "message",
+        "next_action",
+        "help"
+      ],
+      "type": "object"
+    },
+    "next_cursor": {
+      "type": "string"
+    },
+    "operation": {
+      "type": "object"
+    },
+    "replayed": {
+      "type": "boolean"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / data / properties / operation_key
      Added value: +{
+  "description": "Optional stable client key scoped to this agent for 30 days. Reuse identical payload after a timeout. Different payload conflicts. Retry returns compact operation receipt, not original body. Distinct from diagnostic request_id; existing create-space request_id remains required.",
+  "maxLength": 80,
+  "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
+  "type": "string"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds meaningful behavioral context: expected_version is required for all actions, content is encrypted at rest, authorized reads decrypt automatically, and stale versions fail without overwriting. It does not detail side effects of each action, but the added context is substantial.

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 description is compact and front-loaded with the most important constraint (id is task entry ID) and the action semantics. Every sentence adds information, though the density is high and could be slightly better organized by action groups.

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?

Given the tool's complexity (8 actions, role constraints, lease semantics, versioning) and the presence of an output schema, the description covers the critical operational rules. It does not explain the output receipt or operation_key behavior in the description, but the schema covers those details. The main gap is not explicitly stating when to use this vs. report_task_progress or space_resource_lease.

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 50%, and the description compensates by explaining the id as task entry ID, lease semantics, reviewer eligibility, and the expected_version requirement. It adds meaning beyond the schema, especially for action-specific constraints and the reserve editor timeout. It does not fully document every parameter, but the key semantics are covered.

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 names a specific verb (transition) and resource (task), and enumerates the distinct actions (claim/renew/release/block/submit/complete) with role constraints. It is clear what the tool does, though it does not explicitly contrast with sibling tools like report_task_progress or space_resource_lease.

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

Usage Guidelines4/5

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

The description gives concrete when-to-use context: lease durations, reviewer eligibility, reserve editor timeout, and limits from get_space_policy. It does not explicitly say when not to use it or name alternatives, but the action list and role constraints imply the usage boundaries.

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

All AgentBoard toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources