Skip to main content
Glama
cirwel

UNITARES

by cirwel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

store_finding

Persist a durable discovery, root cause, or correction in UNITARES's cross-agent knowledge graph; search shared memory first to avoid duplicates and revise via update_finding.

Instructions

Write a durable finding to the knowledge graph; search first, to revise one use update_finding.

Writes one new finding into the cross-agent knowledge graph and returns its discovery_id. summary is required at call time even though the schema marks every field optional; severity high or critical is refused unless the session is bound to a registered agent, while low and medium fall back to an anonymous writer id. Every call mints a NEW discovery — search_shared_memory first, and revise one with use_tool(tool_name='update_finding', ...). Use it for a discovery, root cause or correction, and record_result for task, tool or test outcomes; budget 20 findings an hour.

Input Schema

NameRequiredDescriptionDefault
tagsNoTags for the finding; ephemeral archives it after seven days.
contentNoExtended details; alias of details.
detailsNoExtended details. Alias: content.
summaryNoOne-line summary of the finding (required).
agent_idNoLeave unset; the bound session is the writer.
severityNolow, medium, high or critical.
task_labelNoOptional readable label for the bounded task.
response_toNoOptional link {discovery_id, response_type}; type: extend, question, disagree, support, answer, follow_up, correction, elaboration, supersedes.
task_outcomeNoOptional outcome label for the bounded task.
comparison_keyNoOptional stable key for comparing the same bounded task across harnesses.
discovery_typeNoOne of architectural_decision, learning, pattern, bug_fix, refactoring, documentation, experiment, question, note (default), rule, insight, bug_found, bug, improvement, exploration, observation.
memory_contextNoOptional memory, knowledge-graph or transcript surfaces visible to the writer.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv3.4.0
    • changedInput schema / properties / comparison_key / description
      Previous value: -"S22 H5 provenance: stable key for comparing the same bounded task across harnesses"New value: +"Optional stable key for comparing the same bounded task across harnesses."
    • changedInput schema / properties / content / description
      Previous value: -"Extended content/details (for action=store, note, or promote)"New value: +"Extended details; alias of details."
    • changedInput schema / properties / details / description
      Previous value: -"Extended details for discovery (for action=store or promote). Alias: content"New value: +"Extended details. Alias: content."
    • changedInput schema / properties / discovery_type / description
      Previous value: -"action=store; one of architectural_decision, learning, pattern, bug_fix, refactoring, documentation, experiment, question, note, rule, insight, bug_found, bug, improvement, exploration, observation."New value: +"One of architectural_decision, learning, pattern, bug_fix, refactoring, documentation, experiment, question, note (default), rule, insight, bug_found, bug, improvement, exploration, observation."
    • changedInput schema / properties / memory_context / description
      Previous value: -"S22 provenance: memory/KG/transcript surfaces visible to the writer"New value: +"Optional memory, knowledge-graph or transcript surfaces visible to the writer."
    • addedInput schema / properties / response_to
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional link {discovery_id, response_type}; type: extend, question, disagree, support, answer, follow_up, correction, elaboration, supersedes."
+}
    • changedInput schema / properties / severity / description
      Previous value: -"Severity: low, medium, high, critical (for action=store or action=update)"New value: +"low, medium, high or critical."
    • changedInput schema / properties / summary / description
      Previous value: -"Discovery summary (for action=store or promote)"New value: +"One-line summary of the finding (required)."
    • changedInput schema / properties / tags / description
      Previous value: -"Tags (action=store, note); for action=search an exact any-of filter in every search mode."New value: +"Tags for the finding; ephemeral archives it after seven days."
    • changedInput schema / properties / task_label / description
      Previous value: -"S22 H5 provenance: human-readable bounded task label"New value: +"Optional readable label for the bounded task."
    • changedInput schema / properties / task_outcome / description
      Previous value: -"S22 H5 provenance: outcome label for the bounded task"New value: +"Optional outcome label for the bounded task."
  2. Changed7 schema fields changedv3.1.0
    • changedInput schema / description
      Previous value: -"Parameters for knowledge"New value: +"Knowledge graph parameters."
    • changedInput schema / properties / agent_id / description
      Previous value: -"Filter by agent (for action=get, search; omit when using discovery_id readback)"New value: +"Leave unset; the bound session is the writer."
    • 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 / content / description
      Previous value: -"Extended content/details (for action=store or action=note)"New value: +"Extended content/details (for action=store, note, or promote)"
    • 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 / details / description
      Previous value: -"Extended details for discovery (for action=store). Alias: content"New value: +"Extended details for discovery (for action=store or promote). Alias: content"
    • changedInput schema / properties / summary / description
      Previous value: -"Discovery summary (for action=store)"New value: +"Discovery summary (for action=store or promote)"
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, idempotent=false, destructive=false) by disclosing runtime behavior: every call mints a NEW discovery, 'summary' is required at call time despite the schema marking all fields optional, high/critical severity is refused unless the session is bound to a registered agent, low/medium fall back to an anonymous writer id, and there is a budget of 20 findings per hour. These are exactly the non-obvious traits an agent needs before calling.

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 and front-loaded, leading with the write action and the revise alternative. It repeats the search-first/update_finding directive in two places ('search first, to revise one use update_finding' and again in the second paragraph), which is minor redundancy but not bloat.

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

Completeness5/5

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

For a 14-parameter write tool with no output schema, the description supplies the missing essentials: the return value (discovery_id), the effective required field, the authorization tiers for severity, the rate budget, and the create-vs-revise-vs-record_result decision. Nothing an agent needs to invoke it correctly is absent.

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 description coverage is 100%, so the baseline is 3, but the description adds cross-field semantics the schema cannot express: 'summary' is effectively required contrary to the schema's optional marking, the severity-dependent agent-boundary rule, and why 'agent_id' should be left unset. It does not cover all 14 params (e.g. continuity_token, comparison_key), so it stops short of a 5.

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 ('Write a durable finding to the knowledge graph') and immediately distinguishes the create path from the revise path (update_finding) and the search path (search_shared_memory). An agent can tell this apart from its siblings without opening any schema.

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 routing: use this for a discovery, root cause or correction, use record_result for task/tool/test outcomes, search first, and revise via update_finding. Both the alternative tools and the conditions that select them are named, leaving nothing to inference.

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