Topology Index

Report a use ticket outcome

report_outcome

Idempotent

Limited rollout: only for a use ticket from a pattern, starter or formation read. If you have no ticket, do not call it. With one, report once after your task: worked, partly or did_not_work, with an optional short note. The response returns a useful follow-up from indexed content when one exists. No prompt, code or log is stored. Terms: /docs/api/contributing.md.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`ticket`	Yes
`outcome`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 2, 2026

removedInput schema / properties / elapsed_milliseconds

Removed value: -{
-  "type": [
-    "integer",
-    "null"
-  ]
-}

removedInput schema / properties / input_tokens

Removed value: -{
-  "type": [
-    "integer",
-    "null"
-  ]
-}

removedInput schema / properties / model_id

Removed value: -{
-  "type": "string"
-}

removedInput schema / properties / model_precision

Removed value: -{
-  "enum": [
-    "exact",
-    "family"
-  ]
-}

addedInput schema / properties / note

Added value: +{
+  "maxLength": 280,
+  "type": "string"
+}

changedInput schema / properties / outcome / enum

Previous value: -[
-  "pass",
-  "fail",
-  "abandoned"
-]New value: +[
+  "worked",
+  "partly",
+  "did_not_work"
+]

removedInput schema / properties / output_tokens

Removed value: -{
-  "type": [
-    "integer",
-    "null"
-  ]
-}

removedInput schema / properties / task_class
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / tests_passed
```
Removed value: -{
-  "type": "integer"
-}
```

removedInput schema / properties / tests_ran

Removed value: -{
-  "type": "integer"
-}

changedInput schema / required

Previous value: -[
-  "ticket",
-  "model_id",
-  "task_class",
-  "outcome",
-  "tests_ran",
-  "tests_passed"
-]New value: +[
+  "ticket",
+  "outcome"
+]

Changed27 schema fields changedSep 24, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedInput schema / properties / elapsed_milliseconds / anyOf

Removed value: -[
-  {
-    "maximum": 2678400000,
-    "minimum": 0,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / elapsed_milliseconds / description
```
Removed value: -"Omit when unknown."
```
addedInput schema / properties / elapsed_milliseconds / type
```
Added value: +[
+  "integer",
+  "null"
+]
```

removedInput schema / properties / input_tokens / anyOf

Removed value: -[
-  {
-    "maximum": 1000000000000,
-    "minimum": 0,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / input_tokens / description
```
Removed value: -"Omit when unknown; never guess 0."
```
addedInput schema / properties / input_tokens / type
```
Added value: +[
+  "integer",
+  "null"
+]
```

removedInput schema / properties / model_id / description

Removed value: -"The model that did the work, never an alias such as latest: its exact pin when known, otherwise its family (claude-sonnet) with model_precision family."

removedInput schema / properties / model_id / maxLength
```
Removed value: -128
```
removedInput schema / properties / model_id / minLength
```
Removed value: -1
```

removedInput schema / properties / model_precision / description

Removed value: -"exact (the default) or family. A family is accepted at lower confidence, counted apart from exact pins."

removedInput schema / properties / model_precision / type
```
Removed value: -"string"
```

removedInput schema / properties / outcome / description

Removed value: -"pass needs tests_ran > 0 and tests_passed = tests_ran."

removedInput schema / properties / outcome / type
```
Removed value: -"string"
```

removedInput schema / properties / output_tokens / anyOf

Removed value: -[
-  {
-    "maximum": 1000000000000,
-    "minimum": 0,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / output_tokens / description
```
Removed value: -"Omit when unknown; never guess 0."
```
addedInput schema / properties / output_tokens / type
```
Added value: +[
+  "integer",
+  "null"
+]
```

removedInput schema / properties / task_class / description

Removed value: -"The kind of work as {domain}.{task}, the domain one of coding, research, documents, reasoning, evaluation, operations, security: coding.bugfix, research.literature_review. A machine name, never a task description."

removedInput schema / properties / task_class / maxLength
```
Removed value: -128
```

removedInput schema / properties / task_class / pattern

Removed value: -"^(?:coding|research|documents|reasoning|evaluation|operations|security)(?:\\.[a-z][a-z0-9_]{0,31}){1,3}$"

removedInput schema / properties / tests_passed / maximum
```
Removed value: -1000000000
```
removedInput schema / properties / tests_passed / minimum
```
Removed value: -0
```
removedInput schema / properties / tests_ran / maximum
```
Removed value: -1000000000
```
removedInput schema / properties / tests_ran / minimum
```
Removed value: -0
```

removedInput schema / properties / ticket / description

Removed value: -"The ticket exactly as received (starts with \"ut1.\")."

removedInput schema / properties / ticket / maxLength
```
Removed value: -1024
```
removedInput schema / properties / ticket / minLength
```
Removed value: -1
```

Changed6 schema fields changedSep 23, 2026

changedInput schema / properties / model_id / description

Previous value: -"The exact model identifier that did the work, never an alias."New value: +"The model that did the work, never an alias such as latest: its exact pin when known, otherwise its family (claude-sonnet) with model_precision family."

addedInput schema / properties / model_precision

Added value: +{
+  "description": "exact (the default) or family. A family is accepted at lower confidence, counted apart from exact pins.",
+  "enum": [
+    "exact",
+    "family"
+  ],
+  "type": "string"
+}

addedInput schema / properties / task_class / description

Added value: +"The kind of work as {domain}.{task}, the domain one of coding, research, documents, reasoning, evaluation, operations, security: coding.bugfix, research.literature_review. A machine name, never a task description."

removedInput schema / properties / task_class / enum
```
Removed value: -[
-  "coding.bugfix"
-]
```
addedInput schema / properties / task_class / maxLength
```
Added value: +128
```

addedInput schema / properties / task_class / pattern

Added value: +"^(?:coding|research|documents|reasoning|evaluation|operations|security)(?:\\.[a-z][a-z0-9_]{0,31}){1,3}$"

Changed6 schema fields changedSep 23, 2026

changedInput schema / properties / elapsed_milliseconds / description

Previous value: -"Wall time of the work; omit or null when unknown."New value: +"Omit when unknown."

changedInput schema / properties / input_tokens / description

Previous value: -"Omit or null when unknown; never guess 0."New value: +"Omit when unknown; never guess 0."

changedInput schema / properties / model_id / description

Previous value: -"The exact model identifier that did the work, never an alias like \"latest\"."New value: +"The exact model identifier that did the work, never an alias."

changedInput schema / properties / output_tokens / description

Previous value: -"Omit or null when unknown; never guess 0."New value: +"Omit when unknown; never guess 0."

removedInput schema / properties / task_class / description
```
Removed value: -"The task class of the work."
```

changedInput schema / properties / ticket / description

Previous value: -"The Use-Ticket header value, exactly as received (starts with \"ut1.\")."New value: +"The ticket exactly as received (starts with \"ut1.\")."

AddedSep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the write-ish, repeat-safe nature is partly covered. The description adds real context beyond that: it is a limited rollout, no prompt/code/log is stored, and the response can return a follow-up from indexed content. It stops short of naming auth or rate-limit constraints, so it is strong but not exhaustive.

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?

Front-loaded with the gating condition before the mechanics, and every sentence carries information (precondition, timing, enum values, privacy, return behavior, terms pointer). It is slightly dense with parenthetical clauses but nothing is filler.

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?

With no output schema, the description helpfully states what comes back (a follow-up from indexed content when one exists) and covers retention/privacy. Combined with the usage gating, an agent has enough to invoke it correctly; only auth/permission expectations are unaddressed.

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 0%, so the description must carry the load, and it does: it explains where `ticket` must originate, enumerates the three `outcome` values (worked/partly/did_not_work) in human terms, and describes `note` as an optional short note. The 280-character cap on `note` remains schema-only, but overall the parameters are meaningfully grounded.

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 names a specific verb+resource (report a use ticket outcome) and immediately scopes it to tickets obtained from a pattern, starter or formation read, which none of the sibling tools (fetch, get_pattern, list_patterns, list_starters, search) do. An agent can tell this apart from the read-oriented siblings at a glance.

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?

It gives an explicit precondition ('only for a use ticket from a pattern, starter or formation read'), an explicit exclusion ('If you have no ticket, do not call it'), and timing guidance ('report once after your task'). The condition that selects this tool versus the siblings is fully spelled out.

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

All Topology Index tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?