Skip to main content
Glama
cirwel

UNITARES

by cirwel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_finding

Update an existing discovery in shared memory by its ID, modify status, severity, or details, and mark it resolved or superseded with resolution notes.

Instructions

Primary workflow name for revising a finding already in shared memory; implemented by knowledge(action='update'). Needs the discovery_id; set status when the finding is resolved or superseded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags (action=store, note); for action=search an exact any-of filter in every search mode.
statusNoStatus filter/update value (open, resolved, archived, superseded)
contentNoExtended content/details (for action=store or action=note)
detailsNoExtended details for discovery (for action=store). Alias: content
summaryNoDiscovery summary (for action=store)
agent_idNoFilter by agent (for action=get, search; omit when using discovery_id readback)
severityNoSeverity: low, medium, high, critical (for action=store or action=update)
discovery_idNoDiscovery ID (for action=get/details, update; the NEW discovery for action=supersede)
superseded_byNoID of the discovery that supersedes this one (for action=update with status=superseded)
discovery_typeNoaction=store; one of architectural_decision, learning, pattern, bug_fix, refactoring, documentation, experiment, question, note, rule, insight, bug_found, bug, improvement, exploration, observation.
continuity_tokenNoOwnership proof from onboard()/identity(), for same-live-process rebinds only. Not a cross-process resume credential.
resolution_notesNoRationale to append when closing or updating a discovery
client_session_idNoIn-session binding id from start_session()/identity(); pass it on same-process calls. Not a cross-process proof.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are present, so the description must carry behavioral disclosure. It names the underlying mechanism and a key prerequisite, but does not disclose overwrite semantics, ownership token requirements, or response behavior. For a mutation tool, this is a notable transparency gap.

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?

Two dense sentences front-load purpose and key constraints with no filler. Every sentence contributes actionable information, and the structure is easy to parse.

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?

With 13 optional parameters, no annotations, and no output schema, the description provides high-level orientation but omits critical operational details like ownership/session token requirements, supersession semantics, and what the caller receives. The schema descriptions compensate partially, but this tool is complex enough that the description alone is not fully complete.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is informed. The description adds meaningful guidance by highlighting that discovery_id is needed and that status should be set when resolved or superseded, which connects to the superseded_by field. Other parameters are left to schema descriptions, which are already complete.

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?

Clearly states it revises an existing finding in shared memory, names the underlying knowledge action='update', and identifies the key prerequisite. This differentiates it from store_finding (new findings) and knowledge (generic dispatcher).

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?

Indicates this is the primary workflow for revising existing findings and gives explicit guidance to set status when resolved or superseded. It does not explicitly exclude alternatives like store_finding, but the 'already in shared memory' phrasing implies the boundary.

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

This server cannot be deployed

Other Tools