Skip to main content
Glama

Server Details

Business-ops MCP for FreedomOS — finance, OKRs, customer scoring, AI agents, content. 250+ tools.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 7 tool updates
    • Addedclaim_cloudflare_preview
    • Addedcreate_payment_link
    • Addedget_cloudflare_hosting_status
    • Addedget_receive_status
    • Changedlist_knowledge2 fields changed
      • changedInput schema / properties / folder / description
        Previous value: -"Optional folder to list contents of (e.g., \"acme-deal\", \"partners\"). Omit to list the root level."New value: +"Optional folder to list contents of (e.g., \"canon\", \"partners\"). Omit to list the root level. Always-on docs live in canon/."
      • changedInput schema / properties / search / description
        Previous value: -"Optional search term to filter files by name"New value: +"Optional name-only filter (filename/slug). Does not search file bodies — use read_knowledge by slug for content."
    • Addedset_company_lifecycle
    • Addedstart_company_receive
  2. 1 tool update
    • Addedshare_playbook
  3. 1 tool update
    • Changedupdate_projection1 field changed
      • changedInput schema / properties / account_name / description
        Previous value: -"Account name to update (must match closely, e.g., \"Software Revenue\", \"AWS Hosting\"). Use get_projections to see exact names first."New value: +"Account name to update. Matches an existing line, or creates it on first write (CASH OUT unless the name is clearly revenue)."
  4. 1 tool update
    • Changedget_team_pulse1 field changed
      • changedInput schema / properties / days / description
        Previous value: -"Lookback window in days (default: 7)"New value: +"Lookback window in days for activity_runs and approval_velocity only (default: 7). pending_cards is always the live queue."
  5. 2 tool updates
    • Changedcreate_key_result5 fields changed
      • changedInput schema / properties / current_value / description
        Previous value: -"Current progress value (default: 0). Do not invent a live number for a quantity FO cannot measure (e.g. Amazon GMV). Bind measure_source, or leave 0."New value: +"THIS calendar month's actual (default: 0). Not YTD, not a future projection. For FCF use get_financial_summary displayed_net_cash_flow; for Amazon deposits use get_monthly_trends Amazon Sales. Do not invent Amazon GMV. Bind measure_source, or leave 0."
      • addedInput schema / properties / description
        Added value: +{
        +  "description": "What the number is (e.g. \"This month cash in minus cash out\"). Agents read this back on get_okrs — do not leave blank for cash KRs.",
        +  "type": "string"
        +}
      • addedInput schema / properties / month
        Added value: +{
        +  "description": "YYYY-MM the current_value belongs to (default: this UTC month). Writes monthly_history. Pass 2026-06 to stamp June, not a Q4 pile.",
        +  "type": "string"
        +}
      • changedInput schema / properties / target_value / description
        Previous value: -"Target value to achieve"New value: +"Target value to achieve. 0 is a valid floor (breakeven / this month FCF ≥ $0). Omit only if you intend the default 100."
      • changedInput schema / properties / title / description
        Previous value: -"Key result title (measurable outcome)"New value: +"Key result title (measurable outcome). Title, unit, and current must name the SAME quantity FO can see."
    • Changedupdate_key_result4 fields changed
      • changedInput schema / properties / current_value / description
        Previous value: -"Current progress value"New value: +"THIS 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."
      • addedInput schema / properties / description
        Added value: +{
        +  "description": "What the number is. Read back on get_okrs.",
        +  "type": "string"
        +}
      • addedInput schema / properties / month
        Added value: +{
        +  "description": "YYYY-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.",
        +  "type": "string"
        +}
      • changedInput schema / properties / target_value / description
        Previous value: -"Target value to achieve"New value: +"Target value to achieve. 0 is a valid monthly floor."
  6. 1 tool update
    • Changedcreate_key_result1 field changed
      • changedInput schema / properties / current_value / description
        Previous value: -"Current progress value (default: 0)"New value: +"Current progress value (default: 0). Do not invent a live number for a quantity FO cannot measure (e.g. Amazon GMV). Bind measure_source, or leave 0."
  7. 2 tool updates
    • Addedredraft_engine_playbooks
    • Addedredraft_playbook_contract
  8. 2 tool updates
    • Changedget_next_priority1 field changed
      • changedInput schema / properties / focus_area / description
        Previous value: -"Optional: focus on a specific tactic category"New value: +"Optional: focus on a specific Playbook category"
    • Changedupdate_my_profile1 field changed
      • changedInput schema / properties / outbound_routes_to_me / description
        Previous value: -"The operator's OWN no-manual-outbound preference (S5). true = \"I personally do outbound\" → the founder-outbound tactic filter is OFF for me; false = \"do NOT route founder manual outbound to me\" → the filter stays ON. Only the operator can set this for themselves; it is never set on behalf of another user."New value: +"The operator's OWN no-manual-outbound preference (S5). true = \"I personally do outbound\" → the founder-outbound Playbook filter is OFF for me; false = \"do NOT route founder manual outbound to me\" → the filter stays ON. Only the operator can set this for themselves; it is never set on behalf of another user."
  9. 2 tool updates
    • Addedagree_playbook
    • Addedget_playbook
  10. 1 tool update
    • Removedgenerate_playbooks
  11. 1 tool update
    • Removedoriginate_content_ideas
  12. 3 tool updates
    • Addedlist_ideas
    • Removedlist_inbox
    • Removedlist_workspace_ideas
  13. 7 tool updates
    • Changedadd_agent_activity3 fields changed
      • addedInput schema / properties / activity / properties / linked_kr_id
        Added value: +{
        +  "description": "Required. The Key Result this loop moves. This work needs a goal. Pick the Key Result this loop moves.",
        +  "type": "string"
        +}
      • changedInput schema / properties / activity / required
        Previous value: -[
        -  "name",
        -  "frequency"
        -]New value: +[
        +  "name",
        +  "frequency",
        +  "linked_kr_id"
        +]
      • addedInput schema / properties / linked_kr_id
        Added value: +{
        +  "description": "Required when activity is supplied flat. This work needs a goal. Pick the Key Result this loop moves.",
        +  "type": "string"
        +}
    • Removedcheck_my_inbox
    • Changeddecide_command_center_item2 fields changed
      • addedInput schema / properties / hired_job_action
        Added value: +{
        +  "description": "Unclosed hired-job cards only: retry the first job once. Required with decision approved on that class. Dismiss is not legal. Accepted briefs are not graduation.",
        +  "enum": [
        +    "retry"
        +  ],
        +  "type": "string"
        +}
      • changedInput schema / properties / hold_until / description
        Previous value: -"Loop-health, once-play timeout, or quiet-alarm hold: future ISO date or YYYY-MM-DD that would prove the card wrong. Required with decision snoozed on those classes."New value: +"Loop-health, once-play timeout, hired-job, or quiet-alarm hold: future ISO date or YYYY-MM-DD that would prove the card wrong. Required with decision snoozed on those classes."
    • Addedget_github_app_status
    • Changedrecalibrate_agent_jd1 field changed
      • changedInput schema / properties / regenerate_activities / description
        Previous value: -"Also regenerate the activity plan (default: false — preserves evolved activities)"New value: +"Also regenerate the activity plan (default: false — preserves evolved activities). Regenerated activities must name a Key Result or they are not loops — create the KR first if none exists."
    • Addedstart_github_app_claim
    • Changedupdate_agent_activity1 field changed
      • addedInput schema / properties / patch / properties / linked_kr_id
        Added value: +{
        +  "description": "Rebind this loop to a Key Result. Pick the Key Result this loop moves. Clearing is not legal — unbind is retire.",
        +  "type": "string"
        +}
  14. 29 tool updates
    • Addedarchive_playbook
    • Addedcreate_playbook
    • Removedcreate_tactic
    • Addedcreate_x_ad_draft
    • Changeddecide_command_center_item2 fields changed
      • addedInput schema / properties / agent_outcome_action
        Added value: +{
        +  "description": "Playing-house / thrash / agent_outcome_flag alarms only: pause plant work. Required with decision approved on that class. Stretch and Dismiss are not legal.",
        +  "enum": [
        +    "pause"
        +  ],
        +  "type": "string"
        +}
      • changedInput schema / properties / hold_until / description
        Previous value: -"Loop-health or once-play timeout hold: future ISO date or YYYY-MM-DD that would prove the card wrong. Required with decision snoozed on those classes."New value: +"Loop-health, once-play timeout, or quiet-alarm hold: future ISO date or YYYY-MM-DD that would prove the card wrong. Required with decision snoozed on those classes."
    • Removeddelete_tactic
    • Addedgenerate_playbooks
    • Removedgenerate_tactics
    • Removedget_tactics
    • Addedget_x_ads_performance
    • Addedlist_playbooks
    • Addedlist_x_ad_accounts
    • Addedlist_x_ad_campaigns
    • Addedposthog_create_vision_scanner
    • Addedposthog_delete_vision_scanner
    • Addedposthog_get_vision_observation
    • Addedposthog_get_vision_scanner
    • Addedposthog_list_vision_observations
    • Addedposthog_list_vision_scanners
    • Addedposthog_scan_session
    • Addedposthog_update_vision_scanner
    • Addedrun_playbook
    • Removedrun_tactic
    • Addedsearch_x_ad_targeting
    • Addedset_x_ad_status
    • Changedupdate_pipeline1 field changed
      • addedInput schema / properties / github_input
        Added value: +{
        +  "description": "Whether this pipeline listens to GitHub weekly digest. Social-post pipelines should be false — a story is submitted from the corpus; receipts use ship_receipt. Changelog may stay true.",
        +  "type": "boolean"
        +}
    • Addedupdate_playbook
    • Removedupdate_tactic
    • Addedupdate_x_ad_budget
  15. 2 tool updates
    • Changeddecide_command_center_item2 fields changed
      • changedInput schema / properties / hold_until / description
        Previous value: -"Loop-health hold: future ISO date or YYYY-MM-DD that would prove the card wrong. Required with decision snoozed on that class."New value: +"Loop-health or once-play timeout hold: future ISO date or YYYY-MM-DD that would prove the card wrong. Required with decision snoozed on those classes."
      • addedInput schema / properties / once_play_action
        Added value: +{
        +  "description": "Once-play timeout cards only: retry the same play once, or retire it. Required with decision approved on that class. Dismiss is not legal.",
        +  "enum": [
        +    "retry",
        +    "retire"
        +  ],
        +  "type": "string"
        +}
    • Addedupdate_live_shopify_theme_file
  16. 4 tool updates
    • Changedcreate_tactic5 fields changed
      • changedInput schema / properties / description / description
        Previous value: -"Detailed description of the tactic"New value: +"Detailed how-to / instructions for the Play"
      • changedInput schema / properties / linked_kr_id / description
        Previous value: -"Optional key-result id the tactic most advances (validated against the company OKRs). If omitted, the most off-track KR of the bound objective is chosen."New value: +"Optional key-result id the Play most advances (validated against the company OKRs). If omitted, the most off-track KR of the bound objective is chosen."
      • changedInput schema / properties / objective_id / description
        Previous value: -"Optional OKR objective UUID to bind this tactic to (validated against this company). If omitted, the binding is auto-inferred from the category→OKR map."New value: +"Optional OKR objective UUID to bind this Play to (validated against this company). If omitted, the binding is auto-inferred from the category→OKR map."
      • changedInput schema / properties / status / description
        Previous value: -"Current status of the tactic"New value: +"Current status of the Play"
      • changedInput schema / properties / title / description
        Previous value: -"The tactic title (e.g., \"LinkedIn Content Strategy\")"New value: +"The Play / Playbook title (e.g., \"X Original Content Playbook\")"
    • Changeddelete_tactic2 fields changed
      • changedInput schema / properties / tactic_id / description
        Previous value: -"ID of the tactic to archive (optional if using tactic_title)"New value: +"ID of the Play to archive (optional if using tactic_title)"
      • changedInput schema / properties / tactic_title / description
        Previous value: -"Title of the tactic to archive (use this or tactic_id)"New value: +"Title of the Play to archive (use this or tactic_id)"
    • Changedgenerate_tactics4 fields changed
      • changedInput schema / properties / lane_id / description
        Previous value: -"Optional lane UUID running these tactics (validated against this company)."New value: +"Optional lane UUID running these Plays (validated against this company)."
      • changedInput schema / properties / linked_kr_id / description
        Previous value: -"Optional key-result id (within the bound objective) the tactics most advance."New value: +"Optional key-result id (within the bound objective) the Plays most advance."
      • changedInput schema / properties / objective_id / description
        Previous value: -"Optional OKR objective UUID to bind these tactics to (validated against this company)."New value: +"Optional OKR objective UUID to bind these Plays to (validated against this company)."
      • changedInput schema / properties / userPrompt / description
        Previous value: -"The focus/request the tactics must address (e.g. \"fill the top of funnel for our pharmacy ICP\")."New value: +"The focus/request the Plays must address (e.g. \"fill the top of funnel for our pharmacy ICP\")."
    • Changedupdate_tactic4 fields changed
      • changedInput schema / properties / linked_kr_id / description
        Previous value: -"Key-result id the tactic most advances (validated against the company OKRs; takes precedence over objective_id, and its parent objective is derived). Unresolvable → binding cleared to null. Omit to leave the existing binding untouched."New value: +"Key-result id the Play most advances (validated against the company OKRs; takes precedence over objective_id, and its parent objective is derived). Unresolvable → binding cleared to null. Omit to leave the existing binding untouched."
      • changedInput schema / properties / objective_id / description
        Previous value: -"OKR objective UUID to re-bind this tactic to (validated against this company); its most off-track key result is chosen. Unresolvable → binding cleared to null. Omit to leave the existing binding untouched."New value: +"OKR objective UUID to re-bind this Play to (validated against this company); its most off-track key result is chosen. Unresolvable → binding cleared to null. Omit to leave the existing binding untouched."
      • changedInput schema / properties / tactic_id / description
        Previous value: -"ID of the tactic to update (optional if using tactic_title)"New value: +"ID of the Play to update (optional if using tactic_title)"
      • changedInput schema / properties / tactic_title / description
        Previous value: -"Title of the tactic to update (use this or tactic_id)"New value: +"Title of the Play to update (use this or tactic_id)"

Frequently Asked Questions

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Finance OS for bootstrapped SaaS, providing MCP tools for transaction recording, projections, alerts, and more through natural language interfaces.
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    AI Agent Mission Control — 200+ MCP tools across 31 domains. Manage agents, experiments, workflows, crews, skills, tools, credentials, approvals, signals, budgets, marketplace, knowledge bases, chatbots, and more. Self-hosted, open-source (AGPL-3.0). Supports stdio + Streamable HTTP/SSE with OAuth 2.0 auth.
    34
    65
    AGPL 3.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Open-source MCP hub providing a single endpoint for AI agents to access dozens of business integrations (CRMs, spreadsheets, telephony, ads) with multi-tenancy, OAuth, and context-efficient tool discovery.
    Apache 2.0
  • A
    license
    A
    quality
    A
    maintenance
    VibOps MCP is the control plane between your AI agents and your GPU infrastructure. 74 tools covering: GPU fleet management (deploy, scale, monitor across NVIDIA, AMD, Intel, AWS, Google, Groq), Agent Infrastructure Control Plane (per-agent GPU cost, budget enforcement, model policies, dependency graph), governance (AI Act, SOC 2, immutable HMAC audit chain), and GPU FinOps (chargeback, waste..)..
    74
    18
    MIT
Try in Browser

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