Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis — Resolve Decision

resolve_decision

Close an open decision as agreed, rejected, deferred, or dropped with one line of reasoning, and copy standing-rule agreements into user_decisions so they are honoured going forward.

Instructions

Close an open decision: agreed, rejected, deferred or dropped.

An agreed decision that reads as a standing rule is also copied into
user_decisions, so it starts being honoured rather than merely recorded.

Args:
    od_id: From review_open_decisions().
    state: agreed | rejected | deferred | dropped
    why:   One line on the reasoning — this is the part you cannot reconstruct later.

Input Schema

NameRequiredDescriptionDefault
whyNo
od_idYes
stateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does real work: it discloses the non-obvious side effect that an agreed standing-rule decision is copied into user_decisions and starts being honoured. It also flags that 'why' is the part you cannot reconstruct later. It stops short of saying whether a resolution can be reversed or re-opened.

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?

Front-loaded with the operation and its state vocabulary, then a single side-effect sentence, then a compact Args block. No filler; each line adds information.

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?

An output schema exists, so return values needn't be explained, and the parameter and side-effect coverage are strong for an unannotated mutation tool. The remaining gap is failure/reversibility behaviour (invalid od_id, re-resolution of an already-closed decision).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description fully compensates: od_id gets provenance ('From review_open_decisions()'), state gets the four legal values that the schema does not encode as an enum, and why gets a purpose note. All three parameters gain meaning not present in the schema.

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?

States a specific verb ('Close an open decision') plus the four terminal states, which pins down the operation exactly. It also implies the counterpart tool by naming review_open_decisions() as the source of od_id, so the agent can separate it from the wider decision-tool family.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage flow is implied rather than stated: od_id 'From review_open_decisions()' tells the agent to review first. But there is no explicit guidance on how this differs from sibling decision tools such as commit_session_decisions, promote_session_decisions or record_decision, nor any when-not-to-use condition.

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

Deploy Server

Other Tools