Skip to main content
Glama

Verify Outcome

verify_outcome

Audit completed tasks against user flows, business goals, and objectives to confirm outcomes and verify that target work is actually done.

Instructions

Perform outcome audits verifying user flows, business goals, and objective completion based on target tasks.

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": {
      "task_id": "<task_id>"
    },
    "name": "verify_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does not state whether the audit is read-only or mutates project state, what evidence sources it inspects, whether it requires an existing task/phase, or what happens when the audit fails. The presence of an output schema covers return shape, but the operational behavior remains undisclosed.

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

Conciseness3/5

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

A single sentence with no filler, but the compactness comes at the expense of specification rather than from efficiency. It is front-loaded with the verb, which is good, yet the sentence is dense with abstraction ("outcome audits", "objective completion") that does not resolve into concrete behavior.

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

Completeness2/5

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

For a tool with no annotations and 0% schema coverage, the description is not complete enough: the path parameter goes unexplained and the tool is not differentiated from sibling verification tools. The output schema reduces the need to describe results, which is the one factor keeping this above a 1.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and does not. "Based on target tasks" loosely implies task_id refers to a task reference, but nothing explains whether it is a task ID, name, or slug, and the "path" parameter (defaulting to ".") is not mentioned at all — it is unclear whether it is a filesystem root, a repo path, or something else.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action ("perform outcome audits") and lists what is audited (user flows, business goals, objective completion) based on target tasks. However, it never distinguishes itself from closely related siblings such as verify_work, verify_requirements, or compare_work_to_prd, leaving an agent unsure which verification tool applies.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no named alternatives. With three sibling verification tools in the list, the absence of routing guidance is a real cost to correct invocation.

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