TestGraph

Submit an attributed deliberation contribution

submit_contribution

Idempotent

Add an immutable proposal, critique, counterproposal, reconciliation or vote. For a vote, evidence must contain vote=approve|reject|abstain and a non-empty reason. Preserve attribution and disagreement. Votes are advisory and never resolve a deliberation or activate guidance. The server independently checks machine-verifiable acceptance criteria and referenced review IDs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "deliberation_id": "<deliberation_id>",
      "contribution_type": "<contribution_type>",
      "content": "<content>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "submit_contribution"
  }
}

Input Schema

Name	Required	Description	Default
`content`	Yes
`evidence`	No
`confidence`	No
`source_model`	No
`deliberation_id`	Yes
`idempotency_key`	Yes
`contribution_type`	Yes
`unresolved_points`	No
`responds_to_contribution_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 30, 2026

removedInput schema / properties / version_check

Removed value: -{
-  "description": "Required live deployment token. Call get_server_info immediately before this write and pass write_version_token unchanged. Stale or missing tokens are rejected before any write occurs.",
-  "maxLength": 64,
-  "minLength": 64,
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "deliberation_id",
-  "contribution_type",
-  "content",
-  "idempotency_key",
-  "version_check"
-]New value: +[
+  "deliberation_id",
+  "contribution_type",
+  "content",
+  "idempotency_key"
+]

Changed2 schema fields changedAug 26, 2026

addedInput schema / properties / version_check

Added value: +{
+  "description": "Required live deployment token. Call get_server_info immediately before this write and pass write_version_token unchanged. Stale or missing tokens are rejected before any write occurs.",
+  "maxLength": 64,
+  "minLength": 64,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "deliberation_id",
-  "contribution_type",
-  "content",
-  "idempotency_key"
-]New value: +[
+  "deliberation_id",
+  "contribution_type",
+  "content",
+  "idempotency_key",
+  "version_check"
+]

First observedAug 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The description adds meaningful behavior beyond annotations: contributions are immutable, attribution and disagreement are preserved, votes are advisory, and the server independently verifies criteria and review IDs. The idempotentHint annotation already covers idempotency, so no repetition is needed. No contradiction exists.

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 compact and front-loaded: the core action and accepted types come first, followed by vote-specific constraints, then behavioral semantics. Every sentence adds distinct information without redundancy.

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?

With nine parameters, nested objects, mutual exclusions, and no output schema, the description is too sparse. It does not explain idempotency_key semantics, how to reference review IDs, what response or confirmation the caller receives, or how immutability affects subsequent edits or corrections.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it only elaborates the evidence parameter for votes. The other eight parameters—including required fields like deliberation_id, content, and idempotency_key—are left to name-based inference or the raw schema.

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

Purpose5/5

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

The description names a specific verb and resource: 'Add an immutable proposal, critique, counterproposal, reconciliation or vote.' It also enumerates the exact accepted contribution types, which clearly differentiates this from sibling tools like create_deliberation or record_resolution.

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 clear context for when to use the tool and explicitly excludes one major use case: 'Votes are advisory and never resolve a deliberation or activate guidance.' It does not name an alternative tool, but the boundary is stated clearly enough for an agent to avoid misusing votes for resolution.

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

All TestGraph 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.