Skip to main content
Glama

freedom-mcp

by com.getfreedomos
OverviewDiscussionsAdmin

Hire agent with context

hire_agent_with_context
Destructive

Open a role with the brief from the interview. Use AFTER walking through the interview. The richer the brief, the better the seat. If get_team_roster.archived already covers the role, call reactivate_agent instead — do not mint a twin.

[sensitive-tier, initiates a multi-step agent process — 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
NameRequiredDescriptionDefault
goalYesThe specific mission this hire will achieve — be as specific as possible, include real numbers
companyIdYesFreedomOS company id to act within (you must be a member). Required for company-scoped tools.
obsessionNoThe ONE demand-path KPI this agent lives or dies by (leads, enrolls, revenue, cash, customers). Not "agents activated" or team-hygiene metrics. Specific with numbers when possible (e.g., "Close the $4,200/mo freedom gap"). Always include — core to a complete JD.
preflightNoOPTIONAL. What the operator must hand over BEFORE this role can start (kind "input": a brand voice doc, a target list, a login the operator shares in Knowledge; each with why it is needed, who grants it, the tool that checks for it — default read_knowledge — and what that tool shows when it is there). Integration access ("access") is derived from the activity plan automatically; list it only for something the plan cannot see. A missing item becomes ONE blocked_on_you card from the role, never a guess.
role_nameYesA descriptive role name (e.g., "YouTube Growth Specialist", "Cash Flow Analyst", "SEO Content Writer")
agent_nameNoOPTIONAL. The exact display name the user explicitly asked for — a single first name (e.g. "Garth" from "name it Garth" / "call it Garth"). Set this ONLY when the user named the agent; leave unset to auto-generate a fitting name. NEVER fold the requested name into role_name.
guardrailsNoWhat this agent should NEVER do (e.g., "Never recommend cutting product investment", "Never ignore cash runway below 3 months"). Always include — core to a complete JD.
first_72_hoursNo3 demand-bound first actions (leads/enroll/outbound/content-to-market/cash/fulfillment). FORBIDDEN: placement audits, governance of inactive agents, fleet ownership maps, agent scoreboards. These become Day 1-3 tasks; hygiene shapes are stripped at write time. Always include — core to a complete JD.
reports_to_nameNoName or role of the team member this agent should report to. Use an existing team member name if one is a natural manager. Say "Linnet" for Chief of Staff, or "founder" for direct-to-founder reporting.
success_metricsYesSpecific, measurable outcomes that define success
domain_expertiseNoRole-specific domain knowledge that makes this agent an expert (frameworks, ratios, best practices specific to this role and industry). Include when available — sharpens the agent's expertise.
reporting_cadenceNoHow often to send updates: weekly, biweekly, monthly, or realtime
personality_traitsNoCommunication style preferences (e.g., "direct", "data-heavy", "encouraging", "concise", "detailed analysis")
required_resourcesNoTools, integrations, or data sources this agent needs. Default documents, briefs, and reports to the FreedomOS Knowledge Base (save_knowledge / read_knowledge — always available, visible in-app); list an EXTERNAL integration (e.g. Google Sheets) only when the role genuinely needs it. Do NOT list Google Docs/Sheets as a default — the agent can request a connector via request_connector and state the limitation until it is granted.
context_and_resourcesNoWhat the user has already tried, existing tools/data/resources available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / domain_expertise / description
      Previous value: -"Role-specific domain knowledge that makes this agent an expert (frameworks, ratios, best practices specific to this role and industry)"New value: +"Role-specific domain knowledge that makes this agent an expert (frameworks, ratios, best practices specific to this role and industry). Include when available — sharpens the agent's expertise."
    • changedInput schema / properties / first_72_hours / description
      Previous value: -"3 demand-bound first actions (leads/enroll/outbound/content-to-market/cash/fulfillment). FORBIDDEN: placement audits, governance of inactive agents, fleet ownership maps, agent scoreboards. These become Day 1-3 tasks; hygiene shapes are stripped at write time."New value: +"3 demand-bound first actions (leads/enroll/outbound/content-to-market/cash/fulfillment). FORBIDDEN: placement audits, governance of inactive agents, fleet ownership maps, agent scoreboards. These become Day 1-3 tasks; hygiene shapes are stripped at write time. Always include — core to a complete JD."
    • changedInput schema / properties / guardrails / description
      Previous value: -"What this agent should NEVER do (e.g., \"Never recommend cutting product investment\", \"Never ignore cash runway below 3 months\")"New value: +"What this agent should NEVER do (e.g., \"Never recommend cutting product investment\", \"Never ignore cash runway below 3 months\"). Always include — core to a complete JD."
    • changedInput schema / properties / obsession / description
      Previous value: -"The ONE demand-path KPI this agent lives or dies by (leads, enrolls, revenue, cash, customers). Not \"agents activated\" or team-hygiene metrics. Specific with numbers when possible (e.g., \"Close the $4,200/mo freedom gap\")."New value: +"The ONE demand-path KPI this agent lives or dies by (leads, enrolls, revenue, cash, customers). Not \"agents activated\" or team-hygiene metrics. Specific with numbers when possible (e.g., \"Close the $4,200/mo freedom gap\"). Always include — core to a complete JD."
    • addedInput schema / properties / preflight
      Added value: +{
+  "description": "OPTIONAL. What the operator must hand over BEFORE this role can start (kind \"input\": a brand voice doc, a target list, a login the operator shares in Knowledge; each with why it is needed, who grants it, the tool that checks for it — default read_knowledge — and what that tool shows when it is there). Integration access (\"access\") is derived from the activity plan automatically; list it only for something the plan cannot see. A missing item becomes ONE blocked_on_you card from the role, never a guess.",
+  "items": {
+    "properties": {
+      "check_tool": {
+        "type": "string"
+      },
+      "granted_by": {
+        "type": "string"
+      },
+      "kind": {
+        "enum": [
+          "input",
+          "access"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "output": {
+        "type": "string"
+      },
+      "why": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / first_72_hours / description
      Previous value: -"The 3 specific actions the agent will take immediately after being hired. These become initial tasks."New value: +"3 demand-bound first actions (leads/enroll/outbound/content-to-market/cash/fulfillment). FORBIDDEN: placement audits, governance of inactive agents, fleet ownership maps, agent scoreboards. These become Day 1-3 tasks; hygiene shapes are stripped at write time."
    • changedInput schema / properties / obsession / description
      Previous value: -"The ONE KPI this agent lives or dies by. Must be specific with numbers from the interview (e.g., \"Close the $4,200/mo freedom gap\")"New value: +"The ONE demand-path KPI this agent lives or dies by (leads, enrolls, revenue, cash, customers). Not \"agents activated\" or team-hygiene metrics. Specific with numbers when possible (e.g., \"Close the $4,200/mo freedom gap\")."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, and the description adds meaningful behavioral context: it initiates a multi-step agent process, has a sensitive tier with approval requirements (executive/gm run without a card, others need approval), and clarifies that connector access still requires an OAuth card. It also instructs to call on the first clear ask without re-asking. This goes beyond the annotations by explaining the approval flow and multi-step nature. Minor deduction: it doesn't detail what the multi-step process entails or what side effects occur beyond hiring.

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 well-structured: the core usage guidance is front-loaded in the first two sentences, followed by the sibling alternative, then the sensitive-tier approval context. Every sentence earns its place, though the sensitive-tier bracket is long and could be slightly more compact. It's appropriately sized for a complex tool with 15 parameters.

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 (15 params, multi-step process, sensitive tier, no output schema), the description covers the key operational context: when to call it, approval requirements, the preflight behavior, and the alternative path. It doesn't describe the return value or what the multi-step process produces, but the schema covers parameters thoroughly. The description is complete enough for an agent to select and invoke it correctly, with minor gaps around post-call expectations.

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 emphasizing the quality of the brief ('The richer the brief, the better the seat') and by clarifying the preflight parameter's purpose and behavior ('A missing item becomes ONE blocked_on_you card from the role, never a guess'). It also adds semantic guidance on agent_name ('Set this ONLY when the user named the agent... NEVER fold the requested name into role_name') and first_72_hours ('FORBIDDEN: placement audits... hygiene shapes are stripped at write time'). This is substantial added meaning 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 opens with a specific verb and resource: 'Open a role with the brief from the interview.' It clearly distinguishes this tool from siblings by stating it should be used AFTER the interview and explicitly names reactivate_agent as the alternative when the role is already covered. This is a clear, specific purpose statement that differentiates it from the 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance: 'Use AFTER walking through the interview.' It also gives a clear exclusion condition: 'If get_team_roster.archived already covers the role, call reactivate_agent instead — do not mint a twin.' This is exemplary usage guidance with a named alternative and a specific condition.

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
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