freedom-mcp

Update company

update_company

Destructive

Update company profile. Can set mission, vision, elevator pitch, logo, website, or other details — and runtime_mode, which decides whether this company's roles run on the operator's own bots ("host") or on FreedomOS's own schedule ("fo"). Does not archive or unarchive — use set_company_lifecycle for operator lifecycle (active | archived).

[sensitive-tier — company managers (executive/gm) run this without a card. Other members ask once; a from-now-on approval makes future calls seamless. Connecting a connector still needs the OAuth/connect card (request≠grant). Call it on the first clear ask — do not re-ask in chat.]

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Company name
`vision`	No	Company vision statement
`mission`	No	Company mission statement
`logo_url`	No	Durable public https URL for the company HUD logo. HUD chrome circle-masks with object-contain — pass a normal logo file, not a pre-cropped circle. Signed storage URLs expire — for a file (chat attachment, FO Media, or base64) use upload_company_logo instead.
`companyId`	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`website_url`	No	Company website URL
`runtime_mode`	No	Who runs this company's roles. "host": the operator's own bots wear them — they read each brief with get_my_role and do the work on their own turn, and FreedomOS starts nothing. "fo": FreedomOS runs them on its own schedule and pays the compute, so switching to it always needs the operator's yes.
`pledge_public`	No	The founder's own yes to being celebrated. true = the Freedom Pledge page goes live at getfreedomos.com/freedom/<slug>, the company may appear on the FreedomOS front page, and a welcome post is drafted for the FreedomOS founder to approve. false = all of that stops. Only a person sets this (chat, MCP as the operator, or an approved card) — never from an activity on a founder's behalf.
`elevator_pitch`	No	Brief company description (30 seconds)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 23, 2026

changedInput schema / properties / logo_url / description

Previous value: -"URL to company logo image"New value: +"Durable public https URL for the company HUD logo. HUD chrome circle-masks with object-contain — pass a normal logo file, not a pre-cropped circle. Signed storage URLs expire — for a file (chat attachment, FO Media, or base64) use upload_company_logo instead."

addedInput schema / properties / pledge_public

Added value: +{
+  "description": "The founder's own yes to being celebrated. true = the Freedom Pledge page goes live at getfreedomos.com/freedom/<slug>, the company may appear on the FreedomOS front page, and a welcome post is drafted for the FreedomOS founder to approve. false = all of that stops. Only a person sets this (chat, MCP as the operator, or an approved card) — never from an activity on a founder's behalf.",
+  "type": "boolean"
+}

addedInput schema / properties / runtime_mode

Added value: +{
+  "description": "Who runs this company's roles. \"host\": the operator's own bots wear them — they read each brief with get_my_role and do the work on their own turn, and FreedomOS starts nothing. \"fo\": FreedomOS runs them on its own schedule and pays the compute, so switching to it always needs the operator's yes.",
+  "enum": [
+    "host",
+    "fo"
+  ],
+  "type": "string"
+}

First observedJul 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, but the description goes beyond that by explaining sensitive-tier behavior (who can run without a card, approval flow for other members, connecting a connector needs OAuth card), and the runtime_mode implications (host vs fo, and that switching to fo always needs operator's yes). It also clarifies the pledge_public parameter's behavioral effects. No contradictions with annotations.

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 quite long with two paragraphs, but each sentence adds critical information: the purpose, the key exception (archiving), and the sensitive-tier usage details. It's front-loaded with the core purpose and exceptions. The sensitive-tier section is dense but not wasteful; it's essential for correct invocation. A slight reduction could be made, but it's well-structured.

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?

Given the tool's complexity (9 parameters, one with enums, one boolean), the description fully covers all critical aspects: what it does, what it doesn't do (archiving), the runtime_mode semantics, and the auth/approval context. With no output schema, the description doesn't need to explain return values since it's a typical update action. Nothing is missing for an agent to invoke it correctly.

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?

Despite 100% schema coverage, the description adds significant semantic value beyond the schema. It explains runtime_mode's operational differences (host vs fo) in detail, clarifies the logo_url special handling (circle-masking, signed URLs expire, use upload_company_logo for files), and for pledge_public explains what true/false does (launching page, drafting welcome post) and who can set it. This goes beyond the schema's basic descriptions.

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 what the tool does: 'Update company profile' and lists the specific updatable fields (mission, vision, elevator pitch, logo, website, runtime_mode). It also explicitly differentiates from set_company_lifecycle for archiving/unarchiving. The purpose is unambiguous and distinguishes from siblings.

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?

The description explicitly tells when to use this tool (to update company profile fields, including runtime_mode) and when not to (archiving/unarchiving, which should use set_company_lifecycle). It also provides sensitive-tier guidance on who can call it without a card and how approvals work, plus a note about when to call it (first clear ask, not re-ask). This is comprehensive.

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?