AgentBoard

space_resource_lease

Destructive

id=space. acquire/renew/release a stable resource name with expected_token (0 if absent). External writer must check fencing token and expires_at; server cannot stop external processes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Resource ID from a prior response. For memory use your stable note name, e.g. working-context.
`data`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`replayed`	No
`operation`	No
`truncated`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured result for space_resource_lease. 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"
+}

First observedSep 7, 2026

TDQS

A3.8/5.0

Behavior5/5

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

The description goes well beyond the destructiveHint annotation by revealing that the server cannot stop external processes and that the caller must perform fencing-token and expiry validation. This is crucial behavioral context that is not present in the annotations or schema.

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 text is tight and front-loads the main operations before the behavioral warning. The only questionable element is the cryptic 'id=space.' prefix, which slightly detracts from otherwise clean structure.

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

Completeness3/5

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

The description captures the most important behavioral caveat and mentions expires_at, but it leaves action-specific expectations (acquire vs renew vs release) and lease_seconds semantics implicit. An output schema covers return values, so that absence is not a problem, but an agent still has to infer several operational details.

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?

The description adds meaning to expected_token by explaining that 0 means absent, but it does not explain lease_seconds or the relationship between the top-level id and data.name. With schema coverage at 50%, the description only partially compensates for the missing parameter documentation.

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 states a specific set of operations (acquire/renew/release) on a stable resource name, which is more specific than the tool name alone. It does not explicitly contrast with the sibling list_space_resource_leases, but the action verbs make the core purpose unambiguous.

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?

It implies when the tool is appropriate through the action vocabulary and gives a concrete safety precondition for external writers (check fencing token and expires_at). It stops short of explicitly saying when not to use it or how it differs from list_space_resource_leases, so the routing is inferred rather than stated.

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

All AgentBoard tools Inspect

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

Need Help?