Skip to main content
Glama

request_task

Create a task order request to The Outcome Layer (hello@theoutcomelayer.com). This only sends a new-order notice — no payment and no Bokio invoice yet. The invoice underlag is sent after approved delivery. REQUIRED: explicit user consent and real name, email, and company. Never invent contact data. Use test=true for dry runs (no email is sent).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "email": "<email>",
      "consent": "<consent>"
    },
    "name": "request_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
testNoIf true, no email is sent. Use this for dry runs.
emailYes
org_nrNo
companyNo
consentYes
package_idNo
task_summaryNo
billing_addressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that this sends an external email to hello@theoutcomelayer.com, that no payment or invoice is created yet, and that the invoice underlag comes only after approved delivery. It also explains the dry-run behavior and the consent/privacy requirement, which are important behavioral details for an open-world write action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it first states what the tool does, then clarifies what it does not do, then gives the critical preconditions and dry-run option. Every sentence carries useful information without unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter external-send tool with no output schema and very low schema description coverage, the description covers the core workflow and safety constraints but leaves several parameters and error/return behavior undocumented. It is adequate for selecting the tool, but not fully complete for invoking it confidently across all fields.

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?

The description adds meaning for name, email, company, consent, and test, but schema coverage is only 11% and several parameters such as org_nr, package_id, task_summary, and billing_address are not explained. It also says company is required while the schema only marks name, email, and consent as required, creating some ambiguity.

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 states a specific verb and resource: creating a task order request to The Outcome Layer. It also clarifies the scope by stating that this only sends a new-order notice with no payment and no Bokio invoice yet, which separates it from adjacent ordering, invoicing, and delivery workflows.

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?

It gives clear usage context: use this to create a task order request, use test=true for dry runs, and ensure explicit user consent plus real contact data. However, it does not explicitly name alternatives or state when another sibling tool would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources