Skip to main content
Glama

freedom-mcp

by com.getfreedomos

update_key_result

Update a key result for the company operator and any agent owning KR progress (progress, assignment, due date, rename, measure binding). Use when work moves a Key Result and you need to log current value, reassign, rename, or bind a measure source. Prefer key_result_id — the parent objective is resolved from the KR row (no fuzzy title search). Title match is a fallback; resolution uses the EXISTING title even when renaming in the same call. A missing/archived KR returns one terminal recovery with live alternatives — do not retry the same args.

[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.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthNoYYYY-MM the current_value belongs to (default: this UTC month when current_value is set). Upserts monthly_history; live current becomes the latest month in history.
titleNoNew display title for the key result (rename)
due_dateNoDue date (YYYY-MM-DD format)
companyIdYesFreedomOS company id to act within (you must be a member). Required for company-scoped tools.
start_dateNoStart date (YYYY-MM-DD format)
assigned_toNoUser ID to assign this KR to. Use "me" or "current_user" to assign to the current user.
descriptionNoWhat the number is. Read back on get_okrs.
objective_idNoID of the parent objective (optional when key_result_id is set — id resolves the parent)
target_valueNoTarget value to achieve. 0 is a valid monthly floor.
current_valueNoTHIS calendar month's actual unless month is set. Not YTD, not a future projection. FCF: get_financial_summary displayed_net_cash_flow. Amazon deposits: get_monthly_trends Amazon Sales.
key_result_idNoStable KR id (preferred). Parent objective is looked up from the KR row across active objectives — do not re-search by fuzzy objective title.
measure_sourceNoBind current progress to a live data source (auto-updated daily by the OKR health sweep). One of: stripe_active_subscribers, stripe_mrr, crm_active_leads. Pass "none" to unbind and return the KR to manual updates.
objective_titleNoTitle of the parent objective (optional when key_result_id is set — id resolves the parent)
key_result_titleNoTitle of the key result to update (use this OR key_result_id) — matched against the CURRENT title, even when also renaming

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden, and it delivers: write-tier approval behavior, missing/archived KR terminal recovery with live alternatives, no-retry instruction, monthly_history upsert semantics, and daily auto-update behavior for bound measure sources. This goes far beyond a generic 'update' description.

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 dense and front-loaded: the first sentence states the action and scope, and every subsequent sentence adds an operational caveat worth knowing. The approval note is compact and highly relevant, and there is no filler or repetition of schema content.

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 mutation tool with no output schema and no annotations, the description is unusually complete. It covers KR resolution order, title-match fallback, failure behavior, approval requirements, monthly history upsert, and current-value semantics. An agent has enough context to select and invoke the tool correctly and avoid retry loops.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds substantial runtime meaning beyond the schema: key_result_id resolves the parent objective without fuzzy search, key_result_title matches the current title even when renaming, current_value means 'THIS calendar month's actual' with concrete FCF/Amazon source guidance, and measure_source binding includes auto-update behavior. This meaningfully exceeds schema-only knowledge.

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 opens with 'Update a key result...' and explicitly enumerates the mutable dimensions: progress, assignment, due date, rename, and measure binding. It also gives the triggering condition ('Use when work moves a Key Result'), which clearly distinguishes this from create_key_result, delete_key_result, and read-only KR 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?

'Use when work moves a Key Result and you need to log current value, reassign, rename, or bind a measure source' is an explicit usage trigger. It also provides resolution guidance (prefer key_result_id, title match is fallback) and warns not to retry a missing/archived KR. However, it does not explicitly name sibling tools or state when not to use this tool, so it stops just 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.

All freedom-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

The tool set is heavily disambiguated by detailed routing descriptions, domain prefixes, and lifecycle verbs, so most tools have a clear intended purpose. However, at 297 tools there are still close pairs and overlapping decision surfaces (e.g., approval workflows, 'what should I work on' readers, multiple finance/ads readers) that require careful description reading to avoid misselection.

Naming Consistency4/5

Naming is predominantly consistent snake_case verb_noun with strong domain prefixes like shopify_, x_, posthog_, and list_/create_/update_ patterns. Minor inconsistencies exist, such as several collection-returning tools using get_ (get_team_members, get_icps, get_okrs) instead of list_, and some generate_ vs create_ vs draft_ verbs, but the pattern is still predictable overall.

Tool Count1/5

297 tools is an extreme outlier and far beyond a usable MCP tool surface. Even a large suite has no justification for this count in one server; the agent would struggle to select among hundreds of similarly descriptive tools, and the natural 3-15 tool range is exceeded by nearly 20x.

Completeness4/5

The individual domains represented — OKRs, CRM/leads, Shopify, content pipelines, ads, PostHog, team hiring, knowledge, finance, and session management — are covered remarkably well with full lifecycle patterns. Minor gaps exist, such as no full deal CRUD, no delete for several Google/Shopify artifacts, and some analytical surfaces being read-heavy, but most workflows can be completed without dead ends.

Resources