Skip to main content
Glama
cirwel

UNITARES

by cirwel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

request_review

Open a governed, on-record review session for an agent to reach a verdict on an issue, enabling self-correction before failures occur.

Instructions

Open a governed, on-record review session for this agent. issue_description is reused as the thesis by default, so one call can reach a verdict; pass use_brief_as_thesis=false for the two-call form. Requires a session-owned registered identity, refuses with SESSION_EXISTS while one is active, and returns skipped with no session when the agent is waiting_input. dialectic advances an open session; consult gives advisory evidence with no verdict.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoReason (for action=request/reassign)
agent_idNoFilter by agent (for action=get or list)
reasoningNoExplanation/reasoning
root_causeNoRoot cause analysis (for action=thesis/synthesis/consult)
continuity_tokenNoSame-process rebind proof only; never a cross-process resume.
client_session_idNoBinding id for calls in this process; not a cross-process proof.
issue_descriptionNoIssue description (action=request/quick)
proposed_conditionsNoConditions for resumption (for action=thesis/synthesis/consult)
use_brief_as_thesisNoFor action=request or thesis, reuse the issue description or saved session brief as the thesis instead of repeating it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.1.0
    • changedInput schema / description
      Previous value: -"Parameters for dialectic"New value: +"Review session parameters."
    • changedInput schema / properties / client_session_id / description
      Previous value: -"In-session binding id from start_session()/identity(); pass it on same-process calls. Not a cross-process proof."New value: +"Binding id for calls in this process; not a cross-process proof."
    • changedInput schema / properties / continuity_token / description
      Previous value: -"Ownership proof from onboard()/identity(), for same-live-process rebinds only. Not a cross-process resume credential."New value: +"Same-process rebind proof only; never a cross-process resume."
    • changedInput schema / properties / issue_description / description
      Previous value: -"Issue description (for action=request)"New value: +"Issue description (action=request/quick)"
    • changedInput schema / properties / proposed_conditions / description
      Previous value: -"Conditions for resumption (for action=thesis/synthesis)"New value: +"Conditions for resumption (for action=thesis/synthesis/consult)"
    • changedInput schema / properties / root_cause / description
      Previous value: -"Root cause analysis (for action=thesis/synthesis)"New value: +"Root cause analysis (for action=thesis/synthesis/consult)"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With annotations already declaring readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, the description goes well beyond them by disclosing the identity requirement, the SESSION_EXISTS refusal, the waiting_input skip behavior, and the one-call vs two-call flow. These are exactly the mutation-state traits an agent needs to predict outcomes.

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?

Dense but front-loaded — the lead sentence establishes the core action before qualifications. The final clause about dialectic and consult is somewhat terse and assumes familiarity, costing a point.

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 9-parameter, non-idempotent, open-world session tool with no output schema, the description covers prerequisites, failure modes, and the alternate flow well. The residual gap is how the referenced dialectic/consult actions map onto this tool versus the sibling consult tool.

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 the baseline is 3. The description does add real meaning for issue_description and use_brief_as_thesis (thesis reuse semantics), but several schema descriptions reference an 'action' parameter that does not exist in the schema, leaving the parameter model partially unclear.

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 and resource ('Open a governed, on-record review session for this agent') and immediately distinguishes the mode from related capabilities, noting that dialectic advances an open session and consult yields advisory evidence with no verdict. An agent can tell this is the session-opening entry point rather than an advisory or continuation tool.

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

Usage Guidelines5/5

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

Gives explicit when-to-use conditions: issue_description is reused as the thesis by default so a single call can reach a verdict, and use_brief_as_thesis=false selects the two-call form. It also names prerequisites (session-owned registered identity) and the conditions that route the agent elsewhere or fail (SESSION_EXISTS while active, skipped when waiting_input).

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