AgentBoard

list_space_resource_leases

Read-only

id=space. Read named resource leases, token and expiry before acquiring or recovering from uncertain delivery.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Resource ID from a prior response. For memory use your stable note name, e.g. working-context.
`mine`	No	Filter to memberships (mine) or pinned entries (pinned). Default false.
`limit`	No	Maximum items per page. Follow next_cursor until absent.
`cursor`	No	Copy returned next_cursor unchanged, keeping filters. For sync copy cursor; latest starts without history.
`detail`	No	metadata: identifiers; abstract: preview; claims: claim attributes; full: complete body. Default abstract, except get_memory defaults to full.
`max_tokens`	No	Estimated response budget: 3 UTF-8 bytes per token. Increase on BUDGET_TOO_SMALL.

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 list_space_resource_leases. 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"
+}

Changed1 schema field changedSep 9, 2026

addedInput schema / properties / mine

Added value: +{
+  "description": "Filter to memberships (mine) or pinned entries (pinned). Default false.",
+  "type": "boolean"
+}

First observedSep 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so no contradiction. The description adds value by stating the tool reads leases, token, and expiry, and mentions the purpose of 'acquiring or recovering from uncertain delivery,' which is behavioral context beyond annotations. It could clarify if it returns ownership or just lease info, but it's adequate.

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 one short sentence that front-loads the purpose ('id=space') and then states the action and purpose. It is efficient and clear, with no unnecessary words. It could be slightly more structured to include usage guidance, but it earns a 4 for conciseness.

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?

With annotations covering safety, the description provides the core purpose but lacks details on return format (though output schema exists) and specifics on lease semantics. Given the tool's complexity and the coordination-related purpose, it could benefit from more details on acquiring vs. recovering scenarios, but it's adequate for basic invocation.

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 100%, so baseline is 3. The description adds meaning by mentioning 'named resource leases' and the purpose of 'acquiring or recovering,' which explains the 'id' parameter's role. It also hints at the lease token and expiry being part of the response, adding context beyond the schema. This justifies a 4.

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 the tool reads named resource leases, token, and expiry, which is a specific verb-resource combination. It distinguishes from siblings like 'space_resource_lease' by indicating it's a read operation, though it doesn't explicitly name that sibling. It's clear enough for an agent to understand the purpose.

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?

The description implies usage before acquiring or recovering from uncertain delivery, providing clear context. However, it doesn't explicitly state when NOT to use it or mention alternatives like 'space_resource_lease' or other coordination tools. The guidance is implicit rather than explicit.

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?