Skip to main content
Glama
Sign In
PatchWarden

PatchWarden

by jiezeng2004-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

safe_finalize_direct_session

Finalize a Direct session to retrieve bounded structured evidence, excluding verbose diffs and log content for a concise output.

Instructions

Finalize a Direct session and return only bounded structured evidence, omitting diff and verification log content.

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": {
      "session_id": "<session_id>"
    },
    "name": "safe_finalize_direct_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_itemsNoMaximum list entries to return per evidence group.
session_idYesDirect session ID to finalize

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations are all false/neutral, providing no safety hints, so the description carries the burden. It adds useful context about output bounds and omitted content, but does not disclose side effects of finalization (e.g., whether the session is marked completed) or what 'bounded' means concretely. This is adequate but not rich.

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?

The description is a single, front-loaded sentence that efficiently conveys the core function and key constraints without any filler.

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?

Given no output schema, the description should explain return values more thoroughly. It states what is omitted but does not describe the structure of the 'bounded structured evidence' or evidence groups. The mention of max_items implies grouping but details are left unsaid, making it sufficient but not fully complete.

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 100% with both parameters clearly described: session_id identifies the session and max_items limits list entries per evidence group. The description's mention of 'bounded' echoes max_items but does not add meaningful new meaning beyond 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?

The description clearly states the tool's action ('Finalize a Direct session') and specifies the output behavior ('return only bounded structured evidence, omitting diff and verification log content'). This distinguishes it from likely sibling tools such as finalize_direct_session, which would provide full evidence including diffs.

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?

The description implies when to use this tool: when you want finalization results without heavy diff/log content. However, it does not explicitly name alternative tools or state when not to use it, so it falls short of a 5.

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