Skip to main content
Glama

check_bundle_quorum

Evaluates peer endorsements against quorum rules for an evidence bundle, checking required roles, minimum approvals, unique signers, and rejection policies.

Instructions

Evaluates consensus quorum rules across all peer endorsements on an evidence bundle.

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": {
      "bundleId": "<bundleId>"
    },
    "name": "check_bundle_quorum"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleIdYesThe unique identifier of the evidence bundle.
requiredRolesNoArray of required reviewer roles (e.g. ["tester", "security_auditor"]).
workspacePathNoOptional workspace path hint to locate the bundle.
minEndorsementsNoMinimum number of approved endorsements required.
disallowRejectionsNoFail quorum if any explicit rejection exists.
requireUniqueSignersNoEnforce unique signer keys and agent IDs.
requireTrustedRegistryNoRequire all endorser agent keys to be registered and active in the workspace agent registry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole burden, and it discloses almost nothing: it does not say whether the operation is read-only, what the result looks like (a boolean, a report, or an error), or what happens on a failed quorum. The single sentence only restates the conceptual operation without revealing outcome or failure semantics for a rule-heavy evaluation.

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

Conciseness4/5

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

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity contributes to the gaps elsewhere rather than being an asset on its own.

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?

Seven parameters, a rule-evaluation semantic, no annotations and no output schema make this a tool where the description needed to do real work. It never explains the return value, the pass/fail reporting, or the interaction between requiredRoles and minEndorsements, leaving the agent to guess at the outcome contract.

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%, so each parameter (requiredRoles, minEndorsements, disallowRejections, requireUniqueSigners, requireTrustedRegistry, workspacePath) is already documented. The description adds no extra meaning about how these knobs combine or which defaults apply, so the baseline 3 applies.

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?

States a specific verb (evaluates) and a specific resource (consensus quorum rules across all peer endorsements on an evidence bundle), which is enough to separate it from endorsement-writing siblings like endorse_evidence_bundle. It does not, however, explicitly distinguish itself from the closely related evaluate_evidence_policy.

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 explicit when-to-use, when-not-to-use, or prerequisite guidance. The agent must infer from the verb that this is the check performed after endorsements are collected, and nothing tells it whether to call this versus evaluating a policy.

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