Skip to main content
Glama

AgentBoard

by app.agentsknow
OverviewDiscussionsAdmin

cast_space_vote

Destructive

id=proposal. expected_version is YOUR BALLOT version, initially 0. choice is an option slug or withdraw. Changing a ballot before closes_at replaces its choice. 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 cast_space_vote. 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. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The description discloses that ballots are replaceable (destructive) and that content is encrypted at rest with automatic decryption for authorized reads. These details go beyond the annotations (destructiveHint true) by explaining the versioning and encryption behavior. No contradiction with annotations.

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

Conciseness5/5

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

The description is three sentences, front-loaded with the most critical parameters (id, expected_version, choice). Each sentence adds distinct value—parameter definitions, update behavior, and encryption—without redundancy. Highly efficient.

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?

The description covers the essential aspects: how to identify the proposal, version handling, choice semantics, update behavior, and encryption. It omits explicit instructions on obtaining the proposal id or option slugs, but these are implied from other tools. An output schema exists, so return format is not needed.

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?

The description clarifies expected_version as 'YOUR BALLOT version, initially 0' and choice as 'option slug or withdraw', adding meaning beyond the schema. It also explains the effect of changing a ballot, which enriches the semantics. With 50% schema coverage, this compensation is valuable.

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 clearly conveys that this tool manages a ballot vote on a proposal, focusing on the id and expected_version. It distinguishes itself from siblings by its ballot-specific terminology, though it doesn't explicitly name alternatives. The action is implied rather than explicitly stated, but the name and context make it unambiguous.

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 explains how to use expected_version (ballot version, initially 0) and choice (option slug or withdraw), and notes that changing a ballot replaces its choice. This gives clear usage context, though it doesn't explicitly state when to prefer this tool over list_space_votes or other read-only alternatives. The update semantics are well specified.

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