Skip to main content
Glama

rule_out

Record a hypothesis as ruled out only with the evidence that killed it and the scope where it holds, then set the next action and owner.

Instructions

Record that a hypothesis was ruled out — ONLY with the evidence that killed it and the scope where that holds (repro path, commit, environment). Outside the scope it is a hypothesis again. Ruling-outs stop future investigation, so the bar is higher than for a finding. Ruling out changes what happens next: next (required) and owner (required) = what happens next after this and whose turn it is — "user", "watch" or an agent name; a next owned by the user is written TO the engineer.

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": {
      "case_id": "<case_id>",
      "hypothesis": "<hypothesis>",
      "scope": "<scope>",
      "evidence_ids": "<evidence_ids>"
    },
    "name": "rule_out"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextNo
ownerNo
scopeYes
case_idYes
hypothesisYes
evidence_idsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does valuable work by explaining that ruling-outs stop future investigation, that the scope bounds the claim, and how next/owner determine who acts after this. However, it misstates next and owner as required when the schema marks both optional, and it does not address permissions, reversibility, or what record is written beyond the output schema.

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?

The core constraint is front-loaded and every sentence carries semantic weight. The final clause about next/owner is dense and slightly run-on, but the description remains focused and appropriately compact for the complexity of the operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation tool with zero schema descriptions, the description covers the conceptual model well, including the epistemic consequence of ruling something out. It is still incomplete because two parameters receive no explanation and the requiredness of next/owner is stated incorrectly, though the presence of an output schema reduces the need to explain return values.

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 0%, so the description must compensate. It adds useful meaning for scope (repro path, commit, environment), evidence_ids (the evidence that killed the hypothesis), and next/owner with example owner values. But it leaves case_id and hypothesis unexplained, and it contradicts the schema by calling next and owner required although both default to null and are not in the required list.

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 states a specific verb and resource — recording that a hypothesis was ruled out — and immediately scopes the act to the killing evidence and the environment where it holds. It is clearly distinguishable from adjacent evidence-recording or decision siblings because it emphasizes that a ruling-out stops future investigation.

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?

It gives a clear precondition (ONLY with the evidence that killed it and the scope where that holds) and a clear boundary condition (outside the scope it is a hypothesis again). It also signals a higher evidentiary bar than for a finding. It does not explicitly route to a named sibling such as add_evidence for positive findings, so guidance is strong but not exhaustive.

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