Nebelus

Define an outcome unit

define_outcome_unit

Create an organization outcome unit, or update it when the code exists (only the fields given change). Outcome units never move money; they measure value for goals and ROI.

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": {
      "code": "<code>"
    },
    "name": "define_outcome_unit"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	Stable lowercase code, e.g. 'ticket_resolved'.
`icon`	No	Optional icon name from the Blueprint icon set.
`name`	No	Display name; required when creating.
`active`	No	Set false to deactivate the unit.
`source`	No	How the unit is recorded (default self_report).
`auto_rule`	No	For auto_rule: {event: run_completed\|tool_invoked\|thread_messages, tool?, min_messages?}.
`description`	No	One line on what counts as one unit.
`minutes_saved`	No	Minutes of human work one unit saves, for ROI.
`value_per_unit`	No	Monetary value of one unit, for ROI.
`billable_unit_code`	No	For billing_mirror: the billable unit's code.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare not read-only, not open-world, not destructive, so the safety profile is partly covered. The description adds meaningful behavior beyond that: partial-update semantics ('only the fields given change') and a scope guarantee ('never move money'), which prevents the agent from assuming financial side effects.

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?

Two tight sentences with the upsert behavior front-loaded and the scope disclaimer second. No filler, and the most decision-relevant facts (create vs update, partial update) come first.

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?

For a mutation tool with no output schema and full schema coverage, the description supplies the upsert model, partial-update rule, and non-financial scope. It stops short of noting permission requirements or conflict/error behavior, but that is a minor gap.

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 coverage is 100%, so the baseline is 3, but the description earns a bump by clarifying the semantics that matter most for the params: which fields change on update and that updates are field-selective rather than replacing the whole unit. The 'code' key's dual create/update role is also explained outside 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?

States a precise verb pair (create or update on upsert) plus the resource ('organization outcome unit') and the key ('when the code exists'). This cleanly separates it from siblings like list_outcome_units and set_agent_outcomes without the agent needing to open a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It implies usage by explaining the upsert trigger ('or update it when the code exists'), which tells the agent this is the single entry point for both create and edit. However, it never names an alternative tool or states when this should not be used (e.g., versus set_goals/set_agent_outcomes), so guidance stays implicit.

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

All Nebelus tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?