freedom-mcp

Delete key result

delete_key_result

Destructive

Archive a key result (safe delete — recoverable, never hard-deleted). The KR is moved out of the objective's live list into a recoverable archive. Identify by title (preferred) or ID; optionally scope by parent objective. If the title is ambiguous it refuses and lists the matches — pass an ID to disambiguate.

[write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time. Call it on the first clear ask; the card is the yes — do not re-ask in chat.]

Input Schema

TableJSON Schema

Name	Required	Description
`reason`	No	Why it is archived (≤300 chars) — recorded on the archived entry and in the audit trail.
`companyId`	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`objective_id`	No	ID of the parent objective (optional)
`key_result_id`	No	ID of the key result (optional if using key_result_title)
`superseded_by`	No	ID of the LIVE key result that replaces this one (same company). Recorded on the archived entry; any agent that later looks the old id up is redirected to it. Use when a KR is being swapped for a better-measured one rather than dropped.
`objective_title`	No	Title of the parent objective, to scope the search (optional)
`key_result_title`	No	Title of the key result to archive (use this or key_result_id)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / reason

Added value: +{
+  "description": "Why it is archived (≤300 chars) — recorded on the archived entry and in the audit trail.",
+  "type": "string"
+}

addedInput schema / properties / superseded_by

Added value: +{
+  "description": "ID of the LIVE key result that replaces this one (same company). Recorded on the archived entry; any agent that later looks the old id up is redirected to it. Use when a KR is being swapped for a better-measured one rather than dropped.",
+  "type": "string"
+}

First observedJul 19, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description discloses significant behavioral traits beyond the annotations: the operation is recoverable (archive not hard-delete), it may refuse and list matches on ambiguity, it handles superseded_by redirection, and it explains the write-tier approval flow. All this adds value beyond the destructiveHint annotation and sets accurate expectations.

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?

The description is well-structured with the core purpose front-loaded. The first paragraph is concise and informative. The second paragraph on approval is somewhat verbose but provides critical operational guidance. No redundant filler; every sentence contributes.

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?

Given the tool's complexity (7 parameters, no output schema, annotations indicating destructiveness), the description covers the essential aspects: identification, disambiguation, scoping, superseded_by, and approval. It doesn't detail how to retrieve archived items, but that's not necessary for calling the tool correctly. Overall complete for the agent's needs.

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?

Though the schema already describes all parameters (100% coverage), the description adds meaningful semantics: it clarifies that title is preferred over ID, explains the disambiguation need for title, and describes the superseded_by field's redirection behavior. This enhances understanding beyond the bare schema definitions.

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 action ('Archive a key result') and the resource, explicitly distinguishing it from a hard delete ('safe delete — recoverable, never hard-deleted'). It goes beyond a simple restatement and adds meaningful detail about the behavior, making its purpose unambiguous relative to other delete/archive tools.

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?

Provides specific usage guidance: how to identify by title or ID, optional scoping by parent objective, and the disambiguation procedure when titles are ambiguous. Also explains approval behavior and when to call it ('Call it on the first clear ask'). However, it does not explicitly contrast with sibling tools like delete_objective, though the safe-delete framing implicitly distinguishes it.

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

All freedom-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?