freedom-mcp

Manage responsibilities

manage_responsibilities

Destructive

Assign, delegate, or revoke responsibility domains for team members. This controls routing — which user receives agent output for specific domains like marketing, finance, etc.

Routing: Use for "Sarah handles marketing" / "route my queue to Nicolas while I'm out" / "I'm taking marketing back"; proactively suggest delegate when a user's queue is very large.

[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
`action`	Yes	assign = give primary ownership of domains; delegate = temporarily route domains from one user to another (supports valid_until for auto-expiry); revoke = remove a domain assignment. To see current routing, call get_routing_overview.
`reason`	No	Why the change is happening (e.g., "vacation", "new hire", "role change")
`domains`	No	Domain names to assign (e.g., ["marketing", "content", "social"]). Use lowercase.
`companyId`	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`valid_until`	No	ISO date string when delegation expires. Only for delegate action. Omit for permanent assignments.
`target_user_email`	No	Email of the user to assign/delegate to. Required for assign and delegate.
`delegation_from_email`	No	Email of the user delegating their responsibilities. Only for delegate action.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

changedInput schema / properties / action / description

Previous value: -"Action to perform"New value: +"assign = give primary ownership of domains; delegate = temporarily route domains from one user to another (supports valid_until for auto-expiry); revoke = remove a domain assignment. To see current routing, call get_routing_overview."

changedInput schema / properties / action / enum

Previous value: -[
-  "assign",
-  "delegate",
-  "revoke",
-  "list"
-]New value: +[
+  "assign",
+  "delegate",
+  "revoke"
+]

First observedJul 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond annotations (readOnly=false, destructiveHint=true), the description discloses write-tier approval behavior, including the difference between from-now-on and just-once approval, and instructs not to re-ask in chat. This adds meaningful operational context about side effects and approval flow that annotations alone do not capture.

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 a clear opening purpose statement, practical usage examples, and a separate approval note. While slightly verbose with the routing examples and approval messaging, each sentence serves a distinct purpose and is appropriately front-loaded.

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), the description compensates with usage examples and approval guidance. It covers when to use, what actions exist, and the operational approval flow. It does not explain return values or all edge cases, but it is sufficiently complete for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, and each parameter has its own detailed description (e.g., action enum explains assign/delegate/revoke). The tool description does not add further parameter-level meaning, so the baseline of 3 is appropriate—it neither detracts nor adds beyond the schema.

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 tool assigns, delegates, or revokes responsibility domains for team members, and explicitly explains it controls output routing. It is specific about the resource (responsibility domains) and the three valid actions, making its purpose unambiguous even among a large sibling list.

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?

The description gives concrete example user phrases ('Sarah handles marketing', 'route my queue to Nicolas while I'm out') and a proactive trigger (suggest delegate when a queue is very large). It does not explicitly name alternative tools or exclusions, but the usage context is clear enough for an agent to know when to invoke 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?