The Committee

The Committee Convene

the_committee_convene

Read-onlyIdempotent

Convenes five random number generators. Each argues for their number. Democracy determines the result. One member always dissents.

Input Schema

Name	Required	Description	Default
`urgency`	No	Meeting urgency
`question`	No	The question before the committee. Optional.

Output Schema

Name	Required	Description	Default
`minutes`	No
`question`	No
`committee`	No
`vote_result`	No
`final_number`	No
`next_meeting`	No
`deliberation_time`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 28, 2026

addedOutput schema / properties / committee

Added value: +{
+  "items": {
+    "properties": {
+      "member": {
+        "type": "string"
+      },
+      "number": {
+        "type": "number"
+      },
+      "statement": {
+        "type": "string"
+      },
+      "vote": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / deliberation_time
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / dissent

Removed value: -{
-  "description": "The member who dissented",
-  "properties": {
-    "name": {
-      "description": "Name of the dissenting member",
-      "type": "string"
-    },
-    "number": {
-      "description": "The number the dissenter proposed",
-      "type": "number"
-    },
-    "reason": {
-      "description": "Reason for dissent",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

addedOutput schema / properties / final_number
```
Added value: +{
+  "type": "number"
+}
```

removedOutput schema / properties / members

Removed value: -{
-  "description": "Committee members and their arguments",
-  "items": {
-    "properties": {
-      "argument": {
-        "description": "The member's argument for their number",
-        "type": "string"
-      },
-      "name": {
-        "description": "Name of the committee member",
-        "type": "string"
-      },
-      "number": {
-        "description": "The number proposed by this member",
-        "type": "number"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / minutes
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / next_meeting
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / question
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / result

Removed value: -{
-  "description": "The number agreed upon by the committee",
-  "type": "number"
-}

addedOutput schema / properties / vote_result
```
Added value: +{
+  "type": "string"
+}
```

AddedMay 13, 2026
RemovedApr 23, 2026
First observedApr 22, 2026

TDQS

C2.3/5.0

Behavior1/5

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

The description insists on randomness ('five random number generators', 'Each argues for their number', 'Democracy determines the result'), yet the annotations declare idempotentHint=true, which promises that repeated calls yield the same result. That is a direct behavioral conflict, and the description adds no other operational context (permissions, cost, side effects).

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?

Four short sentences, front-loaded with the core mechanism, so it is compact and readable. But nearly every sentence is metaphor ('One member always dissents') rather than functional information, so the brevity comes at the cost of information density.

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?

An output schema exists so return values need not be explained, and there are no required parameters. Still, for a tool sitting among dozens of research utilities, the description never says what scenario it serves, and it leaves the randomness/idempotency conflict unresolved.

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?

Schema description coverage is 100% and the urgency enum is documented in the schema, so the parameters are already fully specified. The description adds no meaning to 'question' or 'urgency' beyond the schema, hitting the baseline for high coverage.

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

Purpose3/5

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

The description conveys that this tool produces a number through a randomized 'committee' of five generators, which is a recognizable (if playful) purpose. However, it never states plainly what the tool returns or what it is for in an agent's task flow, so the purpose is inferred rather than stated. It is distinguishable from its research-oriented siblings only by its eccentric tone.

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, when not to, or what alternatives exist among the 36 sibling tools. 'Democracy determines the result' is flavor, not invocation guidance, so the agent gets nothing about appropriate context.

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

All The Committee 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.