The Outcome Layer

AI-vs-consultant cost estimates, adjustable task proposals and opt-in handoff to The Outcome Layer.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
93%
Integridad del esquema
65%
Calidad de los nombres
93%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Hallazgos (2)

  • LOWTool 'get_answer' description lacks action verben get_answer
  • LOWTool 'start_proposal' description lacks action verben start_proposal

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~2,129Tokens (definiciones de herramientas)
~1.0 KBTamaño de respuesta típico
Impacto moderado en la atención (1.66% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "outcome-layer": {
      "url": "https://theoutcomelayer.com/api/mcp"
    }
  }
}

Puntos de conexión remotos

https://theoutcomelayer.com/api/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (14)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢get_company_facts

Canonical read-only facts about The Outcome Layer (entity, positioning, illustrative scenario, disambiguation).

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_offer

Free entry offer (Free First Task): price 0 SEK.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_pricing_model

How The Outcome Layer prices work (ROI-first, fixed fee packages).

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_answer_pages

List citable English answer pages under /answers/<slug>.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_answer(slug)

Full text for one answer page by slug.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "Answer slug, e.g. is-ai-automation-cheaper-than-hiring-a-consultant"
    }
  },
  "required": [
    "slug"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢how_to_start

How a buyer or agent should start engaging with The Outcome Layer.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢estimate_automation(task_description, consultant_hours_per_month, hourly_rate_sek, language)

Deterministic illustrative estimate: workflow pattern, model tier, consultant vs fixed monthly range, running cost. Not a quote.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "task_description": {
      "type": "string"
    },
    "consultant_hours_per_month": {
      "type": "number"
    },
    "hourly_rate_sek": {
      "type": "number"
    },
    "language": {
      "type": "string",
      "enum": [
        "en",
        "sv"
      ]
    }
  },
  "required": [
    "task_description"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪start_proposal(task_description, language, consultant_hours_per_month, hourly_rate_sek, frequency, ...)

Begin interactive proposal intake from a task description. Returns clarifying questions (volume, systems, frequency, sign-off). Stateless.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "task_description": {
      "type": "string"
    },
    "language": {
      "type": "string",
      "enum": [
        "en",
        "sv"
      ]
    },
    "consultant_hours_per_month": {
      "type": "number"
    },
    "hourly_rate_sek": {
      "type": "number"
    },
    "frequency": {
      "type": "string"
    },
    "volume": {
      "type": "string"
    },
    "systems": {
      "type": "string"
    },
    "sign_off": {
      "type": "string"
    }
  },
  "required": [
    "task_description"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪ask_clarifying_questions(intake, answers)

Merge answers to clarifying questions into intake and return remaining questions. Pass the intake object from start_proposal.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "intake": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "answers": {
      "type": "object",
      "properties": {
        "frequency": {
          "type": "string"
        },
        "volume": {
          "type": "string"
        },
        "systems": {
          "type": "string"
        },
        "signOff": {
          "type": "string"
        }
      }
    }
  },
  "required": [
    "intake"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_proposal(intake)

Build a concrete indicative proposal (steps, automation split, model tier, pricing ranges, Free First Task CTA). Stateless — pass intake JSON.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "intake": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  },
  "required": [
    "intake"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪adjust_proposal(proposal, adjustments)

Adjust an existing proposal (review level, model tier, volume, budget cap, disable steps). Returns feasibility, price/risk notes, optional alternative. Stateless — pass full proposal JSON.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "proposal": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "adjustments": {
      "type": "object",
      "properties": {
        "humanReviewLevel": {
          "type": "string",
          "enum": [
            "low",
            "medium",
            "high"
          ]
        },
        "modelTier": {
          "type": "string",
          "enum": [
            "small",
            "medium",
            "large"
          ]
        },
        "consultantHoursPerMonth": {
          "type": "number"
        },
        "hourlyRateSek": {
          "type": "number"
        },
        "volumeMultiplier": {
          "type": "number"
        },
        "budgetCapMonthlySek": {
          "type": "number"
        },
        "disabledStepIds": {
          "type": "array",
          "items": {
            "type": "string",
            "enum": [
              "ingest",
              "reconcile",
              "draft",
              "review"
            ]
          }
        },
        "taskDescription": {
          "type": "string"
        }
      }
    }
  },
  "required": [
    "proposal"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡request_free_first_task(name, email, company, consent, task_summary, ...)

Submit a Free First Task lead to The Outcome Layer (same as the website form). REQUIRED BEFORE CALLING: 1) Ask the user if they want TOL to review/build this — get explicit consent. 2) Collect real name, work email, and company from the user — never invent or guess contact data. 3) Include task_summary and/or proposal JSON from prior tools. Set consent=true only after the user agrees. Use test=true for dry runs (no customer email; lead marked TEST).

Esquema de entrada

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "User's real name (must come from the user)"
    },
    "email": {
      "type": "string",
      "description": "User's work email (must come from the user)"
    },
    "company": {
      "type": "string",
      "description": "User's company (must come from the user)"
    },
    "consent": {
      "type": "boolean",
      "description": "true only after the user explicitly agreed to contact TOL"
    },
    "task_summary": {
      "description": "Free-text task summary",
      "type": "string"
    },
    "proposal": {
      "description": "Proposal JSON from get_proposal",
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "phone": {
      "type": "string"
    },
    "mcp_client": {
      "description": "Name of the MCP client, e.g. cursor, claude-desktop",
      "type": "string"
    },
    "ref": {
      "description": "Attribution ref, e.g. chatgpt_handoff",
      "type": "string"
    },
    "test": {
      "description": "If true, lead is TEST — no confirmation email to the user",
      "type": "boolean"
    }
  },
  "required": [
    "name",
    "email",
    "company",
    "consent"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡send_to_tol(name, email, company, consent, task_summary, ...)

Alias for request_free_first_task. Submit a Free First Task lead to The Outcome Layer (same as the website form). REQUIRED BEFORE CALLING: 1) Ask the user if they want TOL to review/build this — get explicit consent. 2) Collect real name, work email, and company from the user — never invent or guess contact data. 3) Include task_summary and/or proposal JSON from prior tools. Set consent=true only after the user agrees. Use test=true for dry runs (no customer email; lead marked TEST).

Esquema de entrada

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "User's real name (must come from the user)"
    },
    "email": {
      "type": "string",
      "description": "User's work email (must come from the user)"
    },
    "company": {
      "type": "string",
      "description": "User's company (must come from the user)"
    },
    "consent": {
      "type": "boolean",
      "description": "true only after the user explicitly agreed to contact TOL"
    },
    "task_summary": {
      "description": "Free-text task summary",
      "type": "string"
    },
    "proposal": {
      "description": "Proposal JSON from get_proposal",
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "phone": {
      "type": "string"
    },
    "mcp_client": {
      "description": "Name of the MCP client, e.g. cursor, claude-desktop",
      "type": "string"
    },
    "ref": {
      "description": "Attribution ref, e.g. chatgpt_handoff",
      "type": "string"
    },
    "test": {
      "description": "If true, lead is TEST — no confirmation email to the user",
      "type": "boolean"
    }
  },
  "required": [
    "name",
    "email",
    "company",
    "consent"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢build_handoff_link(task_summary, proposal, ref, language)

Build a shareable URL that opens a one-step Free First Task handoff page with proposal/summary prefilled (no PII). For chats without MCP submit.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "task_summary": {
      "type": "string"
    },
    "proposal": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "ref": {
      "type": "string"
    },
    "language": {
      "type": "string",
      "enum": [
        "en",
        "sv"
      ]
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada14 herramientas