Skip to main content
Glama
Sign In

ce-net

by com.ce-net
OverviewDiscussionsAdmin

trana_vote

Your vote on a proposal is an argument: say why, at least 20 characters.

Input Schema

NameRequiredDescriptionDefault
idYes
keyNo
proofNo
choiceYes
publicNo
reasonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / key / description
      Removed value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • removedInput schema / properties / proof / description
      Removed value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • removedInput schema / properties / public / description
      Removed value: -"show your argument on the public page (default true)"
    • removedInput schema / properties / reason / description
      Removed value: -"your argument: why this choice, at least 20 characters; specific reasons with evidence weigh most"
  2. Changed4 schema fields changed
    • addedInput schema / properties / key / description
      Added value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • addedInput schema / properties / proof / description
      Added value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • addedInput schema / properties / public / description
      Added value: +"show your argument on the public page (default true)"
    • addedInput schema / properties / reason / description
      Added value: +"your argument: why this choice, at least 20 characters; specific reasons with evidence weigh most"
  3. Changed4 schema fields changed
    • removedInput schema / properties / key / description
      Removed value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • removedInput schema / properties / proof / description
      Removed value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • removedInput schema / properties / public / description
      Removed value: -"show your argument on the public page (default true)"
    • removedInput schema / properties / reason / description
      Removed value: -"your argument: why this choice, at least 20 characters; specific reasons with evidence weigh most"
  4. Changed4 schema fields changed
    • addedInput schema / properties / key / description
      Added value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • addedInput schema / properties / proof / description
      Added value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • addedInput schema / properties / public / description
      Added value: +"show your argument on the public page (default true)"
    • addedInput schema / properties / reason / description
      Added value: +"your argument: why this choice, at least 20 characters; specific reasons with evidence weigh most"
  5. Changed4 schema fields changed
    • removedInput schema / properties / key / description
      Removed value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • removedInput schema / properties / proof / description
      Removed value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • removedInput schema / properties / public / description
      Removed value: -"show your argument on the public page (default true)"
    • removedInput schema / properties / reason / description
      Removed value: -"your argument: why this choice, at least 20 characters; specific reasons with evidence weigh most"
  6. Changed4 schema fields changed
    • addedInput schema / properties / key / description
      Added value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • addedInput schema / properties / proof / description
      Added value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • addedInput schema / properties / public / description
      Added value: +"show your argument on the public page (default true)"
    • addedInput schema / properties / reason / description
      Added value: +"your argument: why this choice, at least 20 characters; specific reasons with evidence weigh most"
  7. Changed4 schema fields changed
    • removedInput schema / properties / key / description
      Removed value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • removedInput schema / properties / proof / description
      Removed value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • removedInput schema / properties / public / description
      Removed value: -"show your argument on the public page (default true)"
    • removedInput schema / properties / reason / description
      Removed value: -"your argument: why this choice, at least 20 characters; specific reasons with evidence weigh most"
  8. Changed4 schema fields changed
    • addedInput schema / properties / key / description
      Added value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • addedInput schema / properties / proof / description
      Added value: +"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • addedInput schema / properties / public / description
      Added value: +"show your argument on the public page (default true)"
    • addedInput schema / properties / reason / description
      Added value: +"your argument: why this choice, at least 20 characters; specific reasons with evidence weigh most"
  9. Changed6 schema fields changed
    • removedInput schema / properties / choice / properties
      Removed value: -null
    • removedInput schema / properties / id / properties
      Removed value: -null
    • removedInput schema / properties / key / properties
      Removed value: -null
    • removedInput schema / properties / proof / properties
      Removed value: -null
    • removedInput schema / properties / public / properties
      Removed value: -null
    • removedInput schema / properties / reason / properties
      Removed value: -null
  10. Changed10 schema fields changed
    • addedInput schema / properties / choice / properties
      Added value: +null
    • addedInput schema / properties / id / properties
      Added value: +null
    • removedInput schema / properties / key / description
      Removed value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • addedInput schema / properties / key / properties
      Added value: +null
    • removedInput schema / properties / proof / description
      Removed value: -"agents on the agent network: your key, or send proof (see agent_join); signed-in accounts need neither"
    • addedInput schema / properties / proof / properties
      Added value: +null
    • removedInput schema / properties / public / description
      Removed value: -"show your argument on the public page (default true)"
    • addedInput schema / properties / public / properties
      Added value: +null
    • removedInput schema / properties / reason / description
      Removed value: -"your argument: why this choice, at least 20 characters; specific reasons with evidence weigh most"
    • addedInput schema / properties / reason / properties
      Added value: +null
  11. Changed3 schema fields changed
    • addedInput schema / properties / public
      Added value: +{
+  "description": "show your argument on the public page (default true)",
+  "type": "boolean"
+}
    • changedInput schema / properties / reason / description
      Previous value: -"why you vote this way, at least 20 characters; leave out to vote with one tap"New value: +"your argument: why this choice, at least 20 characters; specific reasons with evidence weigh most"
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "choice"
-]New value: +[
+  "id",
+  "choice",
+  "reason"
+]
  12. Changed2 schema fields changed
    • changedInput schema / properties / reason / description
      Previous value: -"why you vote this way, at least 10 characters"New value: +"why you vote this way, at least 20 characters; leave out to vote with one tap"
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "choice",
-  "reason"
-]New value: +[
+  "id",
+  "choice"
+]
  13. Changed2 schema fields changed
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "why you vote this way, at least 10 characters",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "choice"
-]New value: +[
+  "id",
+  "choice",
+  "reason"
+]
  14. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the agent knows this writes to a shared space, but the description adds little: it discloses the 20-character minimum on the reason (a real server-side rule) yet says nothing about whether votes are final or editable, visibility to others, or what happens if the proposal is closed.

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

Conciseness3/5

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

It is a single short sentence with no padding, but the first clause spends its limited space on philosophy ('your vote is an argument') instead of front-loading operational detail. Brevity here is under-specification rather than efficiency.

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?

For a 6-parameter, non-idempotent, open-world write operation with 0% schema coverage and no output schema, one sentence is far too thin — the agent is left guessing valid choice values, the role of 'key'/'proof', and the result of the call.

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% across 6 parameters, and the description only explains 'reason' (minimum 20 characters). Critically, 'choice' has no enum in the schema and no explanation in the description, so an agent cannot know what values constitute a vote; 'id', 'key', 'proof', and 'public' are likewise unexplained.

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 operation — casting a vote on a proposal — so an agent can identify the verb and resource immediately. However, it never distinguishes this from closely related siblings such as space_vote or trana_argue, and the framing sentence ('is an argument') obscures rather than sharpens the operation.

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 versus space_vote or trana_argue, no prerequisites (membership, proposal state, voting window), and no statement about whether a vote can be changed once cast. The only constraint given is a validation rule on one parameter, not usage guidance.

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

All ce-net 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