Skip to main content
Glama

score_dissent

Record or revise an advisory dissent outcome (vindicated, refuted, or untested) on a frozen contract; only the orchestrator can score, and scores remain display-only.

Instructions

Record or revise an advisory dissent outcome on a frozen contract. Only its orchestrator may score. Scores are display-only and never weight votes or consent.

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": {
      "contract_id": "<contract_id>",
      "orchestrator": "<orchestrator>",
      "dissent_id": "<dissent_id>",
      "outcome": "<outcome>"
    },
    "name": "score_dissent"
  }
}

Input Schema

NameRequiredDescriptionDefault
outcomeYes
dissent_idYes
contract_idYesThe contract id (ctr-<6 characters>-<n>) from propose_contract.
orchestratorYesYour name as this contract's orchestrator (e.g. main). Only the orchestrator that proposed a contract can amend or freeze it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

The description is consistent with the supplied annotations (readOnlyHint=false, destructiveHint=false) and adds context those annotations do not carry: a permission rule (only the orchestrator may score) and the crucial non-effect that scores are display-only and never weight votes or consent. It does not explain what revising an existing score overwrites or what happens if the dissent_id is unknown, which keeps it below 5.

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?

Three short sentences, front-loaded with the action, followed by the permission gate and then the effect disclaimer. No filler, hedging, or repeated restatement of the title.

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?

For a four-required-parameter mutation with no output schema, the definition covers action, precondition, authorization, and the notable absence of governance consequences. Missing: the revise/overwrite behavior and whether the target dissent must already exist, which matter for correct invocation.

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 coverage is 50%: contract_id and orchestrator are documented inline, while outcome and dissent_id rely on a self-describing enum and pattern. The description reuses 'dissent outcome' and 'frozen contract' but adds no format, validity, or error semantics for the undocumented parameters, so it neither compensates for nor deepens the schema.

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 set ('record or revise') and resource ('advisory dissent outcome') with a scope qualifier ('on a frozen contract'), which tells an agent this operates on already-frozen contracts rather than open ones. It does not name a sibling such as file_dissent to disambiguate filing a dissent from scoring one, so the differentiation is only implicit.

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?

Provides the two conditions that gate use: the contract must be frozen, and the caller must be that contract's orchestrator. 'Record or revise' also signals both first-time scoring and later amendment. It stops short of explicitly excluding or routing to an alternative such as file_dissent when no dissent exists yet.

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