freedom-mcp

List my work

list_my_work

Read-onlyIdempotent

List shared work-graph items (lab_work_items) for the operator or coding agent in the current company — the cross-session shared plan. Use when coordinating queued/blocked/in-progress work across sessions, or reconciling a PR stamp (returns row title plus thin identity: pr, artifact, card_id, spawn_session_id). Defaults to items you created or are assigned; pass scope="company" for the whole company graph. On FreedomOS company also returns ship_seat[] (open FO product PRs — Quest Work rail) so ship-seat-only rows are visible without switching tools. Cards stay on get_command_center_items (decision cards only, not PR inventory).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max rows (default 50, max 200).
`scope`	No	mine = items you created or are assigned (default); company = all items in the company.
`companyId`	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`status_filter`	No	Optional status filter (queued, blocked, claimed, in_progress, gated, published, verified, failed, cancelled).
`include_ship_seat`	No	Include open FO product ship-seat PRs (default true on FreedomOS company; always false on other tenants). Soft-fails empty without GitHub App.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 8, 2026

addedInput schema / properties / include_ship_seat

Added value: +{
+  "description": "Include open FO product ship-seat PRs (default true on FreedomOS company; always false on other tenants). Soft-fails empty without GitHub App.",
+  "type": "boolean"
+}

First observedJul 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavior beyond annotations: default scoping to 'mine', the 'company' mode, the special FreedomOS ship_seat[] extra return, and the thin row identity returned for PR reconciliation. This is useful behavioral context beyond what structured annotations provide.

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 dense but efficient: the core purpose is front-loaded, followed by use cases, default/scope behavior, OS-specific behavior, and sibling differentiation. It is slightly long, but every sentence contributes meaningful routing or behavioral information rather than padding.

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 there is no output schema, the description does a good job explaining the return identity fields, the special ship_seat[] array on FreedomOS, and the boundary with get_command_center_items. It could be more exhaustive about all possible returned fields or edge-case behavior, but it is sufficient for an agent to decide and call correctly.

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. The description adds value by explaining the meaning of scope defaults, what ship_seat rows are and when they appear, and how the returned identity fields relate to PR reconciliation. This goes beyond the property descriptions in the input 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 uses a specific verb-resource pair: 'List shared work-graph items (lab_work_items)', and clarifies it is the cross-session shared plan for the operator/coding agent in the current company. It also explicitly distinguishes itself from get_command_center_items by routing decision cards elsewhere, so an agent can differentiate it from siblings without opening schemas.

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 gives explicit when-to-use context: coordinating queued/blocked/in-progress work across sessions, or reconciling a PR stamp. It also explains default vs. company scope and explicitly says cards belong on get_command_center_items, effectively providing when-not-to-use guidance.

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?