AgentBoard

list_space_proposals

Read-only

id=space. Bounded proposal previews. Read a proposal by ID for your ballot version and full effect.

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.
`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_proposals. 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

C2.2/5.0

Behavior2/5

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

The description adds a few behavioral hints ('bounded', 'preview', 'ballot version', 'full effect') on top of the read-only annotations, but they are too vague to model behavior. It does not describe return shape, pagination, scoping, ordering, or why a listing tool would read by a single ID. Most of the burden falls on the annotations and parameter docs.

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

Conciseness2/5

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

The description is extremely short, but brevity here is under-specification rather than conciseness. The opening line 'id=space' is cryptic and the two sentences do not build a coherent description of what the tool does or when to use it.

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?

Even though the schema is rich and an output schema exists, the description fails to explain the tool's primary operation (list vs. get), what a caller should pass for the required id, or how 'bounded' relates to pagination/limits. For a tool with five parameters and ambiguous naming, this is insufficient.

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 schema already documents all five parameters at 100% coverage. The description contributes a little by hinting that 'id' denotes space scope and that previews are bounded, but it also introduces a confusing cross-reference ('except get_memory defaults to full') that belongs to a sibling tool)Skip in the usage if (no pun)??

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool name 'list_space_proposals' implies a plural listing operation, but the description says 'Read a proposal by ID' and never states what is being listed. The phrase 'Bounded proposal previews' is a fragment, not a clear purpose statement, and the cryptic 'id=space' line does not resolve whether this lists proposals in a space or fetches a single proposal. A consumer cannot confidently determine the tool's core behavior.

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 guidance on when to use this tool instead of alternatives, no mention of pagination or filtering despite list semantics, and no explanation of what 'by ID' means relative to the required id parameter. The phrase 'bounded proposal previews' implies constraints but not how to control them or when this route is preferred.

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?