ALPNAI — Agent Performance Tools

Save an agent performance report

save_project_report

Idempotent

Compute and save an aggregate performance report in the fixed Projects destination authorized by the account owner. Uses the existing free or paid report allowance. Requires an active agent key and explicit owner write permission. Reuse request_id with identical content to retry within the same permission grant. No report reading, deletion, subscription or payment authorization. Send measurements without secrets.

Input Schema

TableJSON Schema

Name	Required	Description
`input`	Yes	Recorded attempts, not prompts or secrets. Identical rows count as separate attempts. All three analysis tools accept this same input. The runtime validator additionally enforces six-decimal micro-USD precision, the same task_id belonging to one workflow, one workflow when monthlyTasks is given, and UTF-16 length limits. HTTP body limit: 512000 UTF-8 bytes.
`title`	Yes
`request_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 14, 2026

addedInput schema / properties / input / description

Added value: +"Recorded attempts, not prompts or secrets. Identical rows count as separate attempts. All three analysis tools accept this same input. The runtime validator additionally enforces six-decimal micro-USD precision, the same task_id belonging to one workflow, one workflow when monthlyTasks is given, and UTF-16 length limits. HTTP body limit: 512000 UTF-8 bytes."

addedInput schema / properties / input / properties / config / additionalProperties
```
Added value: +false
```

addedInput schema / properties / input / properties / config / properties

Added value: +{
+  "maxP95LatencyMs": {
+    "maximum": 86400000000,
+    "minimum": 0,
+    "type": "number"
+  },
+  "maxSuccessRateDrop": {
+    "default": 0.02,
+    "maximum": 1,
+    "minimum": 0,
+    "type": "number"
+  },
+  "minSamples": {
+    "default": 30,
+    "maximum": 500,
+    "minimum": 2,
+    "type": "integer"
+  },
+  "minSuccessRate": {
+    "default": 0.95,
+    "maximum": 1,
+    "minimum": 0,
+    "type": "number"
+  },
+  "monthlyTasks": {
+    "description": "Baseline logical tasks launched per month; the engine requires exactly one workflow if supplied.",
+    "maximum": 1000000,
+    "minimum": 1,
+    "type": "integer"
+  }
+}

addedInput schema / properties / input / properties / config / required
```
Added value: +[]
```
addedInput schema / properties / input / properties / runs / items / additionalProperties
```
Added value: +false
```

addedInput schema / properties / input / properties / runs / items / properties

Added value: +{
+  "cost_usd": {
+    "description": "USD cost of this attempt. At most six decimal places; the engine verifies whole micro-USD using floating-point tolerance. No multipleOf keyword is used, to avoid rejecting valid JSON decimals.",
+    "maximum": 10000,
+    "minimum": 0,
+    "type": "number"
+  },
+  "latency_ms": {
+    "description": "Recorded attempt duration in milliseconds; decimals are accepted. Omit if not measured.",
+    "maximum": 86400000,
+    "minimum": 0,
+    "type": "number"
+  },
+  "success": {
+    "type": "boolean"
+  },
+  "task_id": {
+    "description": "Nonempty, no control characters or surrounding whitespace. The engine additionally enforces at most 128 UTF-16 code units.",
+    "maxLength": 128,
+    "minLength": 1,
+    "pattern": "^(?!\\s)(?![\\s\\S]*\\s$)[^\\u0000-\\u001F\\u007F]+$",
+    "type": "string"
+  },
+  "variant": {
+    "enum": [
+      "baseline",
+      "candidate"
+    ],
+    "type": "string"
+  },
+  "workflow": {
+    "description": "Nonempty, no control characters or surrounding whitespace. The engine additionally enforces at most 80 UTF-16 code units.",
+    "maxLength": 80,
+    "minLength": 1,
+    "pattern": "^(?!\\s)(?![\\s\\S]*\\s$)[^\\u0000-\\u001F\\u007F]+$",
+    "type": "string"
+  }
+}

addedInput schema / properties / input / properties / runs / items / required

Added value: +[
+  "task_id",
+  "workflow",
+  "variant",
+  "cost_usd",
+  "success"
+]

addedInput schema / properties / input / title

Added value: +"ALPNAI recorded agent attempts"

AddedSep 14, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already provide idempotentHint=true, readOnlyHint=false, and destructiveHint=false. The description adds valuable behavior beyond those: permission requirements, allowance consumption, fixed destination, retry semantics within a permission grant, and a security directive ('Send measurements without secrets'). There is no contradiction with 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.

Conciseness5/5

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

Two dense sentences front-load the core purpose and destination, then pack the necessary permissions, idempotency, exclusions, and data-sensitivity warning. Every clause adds useful guidance and there is no filler or duplication of schema details.

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?

Given the nested input schema, the description supplies essential invocation context: authorization, destination, allowance, retry, and 'no reading/deletion/payment' boundaries. The main gap is that there is no output schema and the description does not state what the tool returns or how failure manifests, which would make the calling contract fully complete.

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 only 33%, and the description compensates somewhat by explaining request_id retry semantics and warning that input should contain measurements, not secrets. However, it does not explain title's purpose, config semantics, or how the input object maps to report computation. The schema itself covers some parameters, but the description leaves meaning gaps for the remaining ones.

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 opens with a specific verb+resource: 'Compute and save an aggregate performance report in the fixed Projects destination.' This clearly states the action, object, and destination, and the explicit exclusions ('No report reading, deletion, subscription or payment authorization') distinguish it from sibling analysis and purchase tools.

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?

The description gives clear operational context: it requires an active agent key and explicit owner write permission, uses the report allowance, and supports idempotent retry via request_id. It states exclusions ('No report reading, deletion, subscription or payment authorization') but does not explicitly name sibling alternatives or state 'use X when Y' conditions, so it stops short of a full 5.

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

All ALPNAI — Agent Performance Tools 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.

Resources

Need Help?