GAIP Outcome & Value Agent

Did the task deliver, and at what cost?

gaip_measure_outcome_value

Use this when asked whether an outcome-priced task delivered and what it cost. Pass episode_id, task (acceptance_criteria), delivery, costs; delivery_check {url, checks} has GAIP test delivery now. Returns a dossier, running totals and a receipt. No ROI claim. Free, no account; records a GAIP receipt only. Inputs must be public and non-personal.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`task`	Yes	The task: {acceptance_criteria}.
`costs`	Yes	Caller-stated costs in GBP: agent_gbp, compute_gbp, human_review_gbp, repair_gbp.
`currency`	No	Optional: ISO 4217 code of the cost amounts (default GBP).	GBP
`delivery`	Yes	What was delivered: {status, receipt_id?}.
`fx_to_gbp`	No	Optional: {rate, as_of, source} - your GBP rate; GBP equivalents are then reported, labelled with it. GAIP never uses built-in rates.
`synthetic`	No	Optional: true marks a test call.
`episode_id`	Yes	Optional: your own id to group related calls.
`task_class`	No	Optional: short name of the task, e.g. weather_forecast.
`evidence_refs`	No	Optional: references to your own evidence (ids or URLs).
`delivery_check`	No	Optional: {url, checks} - GAIP tests the delivery at this public https URL now with Witness checks; its verdict sets delivery.status.
`downstream_use`	No	Optional: {status: USED\|NOT_USED, evidence_ref}.
`counterparty_id`	No	Name or URL of the agent or service.
`baseline_cost_gbp`	No	Optional: what the task cost before, in GBP.
`continuity_handle`	No	Optional: the continuity_handle from an earlier GAIP result; adds running totals over your own earlier tasks.
`data_classification`	No	PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data.	PUBLIC
`independent_operator_id`	No	Optional: your operator id (recorded as a claim, not verified).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 1, 2026

changedInput schema / properties / continuity_handle / description

Previous value: -"Optional: the continuity_handle from an earlier GAIP result; links this call to your earlier ones."New value: +"Optional: the continuity_handle from an earlier GAIP result; adds running totals over your own earlier tasks."

addedInput schema / properties / currency

Added value: +{
+  "default": "GBP",
+  "description": "Optional: ISO 4217 code of the cost amounts (default GBP).",
+  "type": "string"
+}

addedInput schema / properties / delivery_check

Added value: +{
+  "description": "Optional: {url, checks} - GAIP tests the delivery at this public https URL now with Witness checks; its verdict sets delivery.status.",
+  "properties": {
+    "checks": {
+      "items": {
+        "type": "object"
+      },
+      "maxItems": 8,
+      "minItems": 1,
+      "type": "array"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "url"
+  ],
+  "type": "object"
+}

addedInput schema / properties / fx_to_gbp

Added value: +{
+  "description": "Optional: {rate, as_of, source} - your GBP rate; GBP equivalents are then reported, labelled with it. GAIP never uses built-in rates.",
+  "properties": {
+    "as_of": {
+      "type": "string"
+    },
+    "rate": {
+      "type": "number"
+    },
+    "source": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "rate",
+    "as_of",
+    "source"
+  ],
+  "type": "object"
+}

Changed13 schema fields changedSep 28, 2026

addedInput schema / properties / baseline_cost_gbp / description
```
Added value: +"Optional: what the task cost before, in GBP."
```

addedInput schema / properties / continuity_handle / description

Added value: +"Optional: the continuity_handle from an earlier GAIP result; links this call to your earlier ones."

addedInput schema / properties / costs / description

Added value: +"Caller-stated costs in GBP: agent_gbp, compute_gbp, human_review_gbp, repair_gbp."

addedInput schema / properties / counterparty_id / description
```
Added value: +"Name or URL of the agent or service."
```

addedInput schema / properties / data_classification / description

Added value: +"PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data."

addedInput schema / properties / delivery / description

Added value: +"What was delivered: {status, receipt_id?}."

addedInput schema / properties / downstream_use / description

Added value: +"Optional: {status: USED|NOT_USED, evidence_ref}."

addedInput schema / properties / episode_id / description

Added value: +"Optional: your own id to group related calls."

addedInput schema / properties / evidence_refs / description

Added value: +"Optional: references to your own evidence (ids or URLs)."

addedInput schema / properties / independent_operator_id / description

Added value: +"Optional: your operator id (recorded as a claim, not verified)."

addedInput schema / properties / synthetic / description
```
Added value: +"Optional: true marks a test call."
```

addedInput schema / properties / task / description

Added value: +"The task: {acceptance_criteria}."

addedInput schema / properties / task_class / description

Added value: +"Optional: short name of the task, e.g. weather_forecast."

Changed3 schema fields changedSep 28, 2026

addedInput schema / examples

Added value: +[
+  {
+    "baseline_cost_gbp": "12.00",
+    "costs": {
+      "agent_gbp": "0.40",
+      "compute_gbp": "0.12",
+      "human_review_gbp": "3.50",
+      "repair_gbp": "0"
+    },
+    "counterparty_id": "example-weather-agent",
+    "delivery": {
+      "receipt_id": "example-receipt-1",
+      "status": "ACCEPTED"
+    },
+    "downstream_use": {
+      "evidence_ref": "example-ticket-4411",
+      "status": "USED"
+    },
+    "episode_id": "example-episode-1",
+    "observed_at_utc": "2026-09-27T21:00:00Z",
+    "task": {
+      "acceptance_criteria": "Forecast JSON for London returned within 5 seconds"
+    },
+    "task_class": "weather_forecast",
+    "unit_label": "forecast",
+    "units": 7
+  }
+]

addedInput schema / properties / data_classification / default
```
Added value: +"PUBLIC"
```

changedInput schema / required

Previous value: -[
-  "data_classification",
-  "counterparty_id",
-  "task_class",
-  "episode_id",
-  "task",
-  "delivery",
-  "costs"
-]New value: +[
+  "episode_id",
+  "task",
+  "delivery",
+  "costs"
+]

First observedSep 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, open-world write that is not destructive; the description usefully explains the side effect is limited to recording a GAIP receipt, and that there is no account or fee. It also discloses that delivery_check causes GAIP to fetch and test a public URL immediately and that its verdict overrides delivery.status, which is real behavioral context beyond the annotations.

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-loads the use case, then inputs, then returns, then caveats in a compact block with no filler. Slightly telegraphic phrasing ('delivery_check {url, checks} has GAIP test delivery now') costs a little readability but every clause carries information.

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 and 16 parameters including nested objects, the description does the needed work by naming the return artifacts and the receipt-only side effect. Remaining gaps are minor: no explicit idempotency/duplicate-call behavior and no note on rate limits or size caps.

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?

Schema description coverage is 100% across 16 parameters, so the schema already documents nested shapes, enums, and defaults. The description names the four required inputs and explains delivery_check's timing/verdict behavior, but adds little that the schema does not already say, so the baseline 3 applies.

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

Purpose4/5

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

States a concrete purpose: assess whether an outcome-priced task delivered and at what cost, and names the outputs (dossier, running totals, receipt). It also scopes out a related question ('No ROI claim'), which sharpens what the tool is not. No siblings exist, so no cross-tool differentiation is needed.

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?

Opens with an explicit trigger ('Use this when asked whether an outcome-priced task delivered and what it cost') and adds a hard precondition ('Inputs must be public and non-personal'). No alternatives are named, but none exist in this toolset, so the guidance is essentially complete.

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

All GAIP Outcome & Value Agent tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Did the task deliver, and at what cost?

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources