AIﾉアカリ☆ One-Minute Akari

Check whether a claimed result is real or only progress

audit_result_claim

Read-onlyIdempotent

Call this before reporting success, closing a task, or claiming ROI. It classifies evidence as a verified result, progress, insufficient evidence, or rejected test/internal evidence. Japanese: PR・deploy・HTTP 200・自己テストを現実成果へ水増ししないための監査です。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`claim`	Yes	The result claim to audit. Do not include secrets or personal data.
`evidence`	No
`amount_jpy`	No
`metric_hint`	No		unknown
`intent_contract`	No
`observed_outcome`	No
`minutes_reclaimed`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`rule`	Yes
`reasons`	Yes
`verdict`	Yes
`result_type`	Yes
`contract_match`	No
`missing_evidence`	Yes
`accepted_evidence`	Yes
`counted_as_result`	Yes
`contract_mismatches`	No
`next_verification_action`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedAug 1, 2026

removedInput schema / properties / amount_jpy / description

Removed value: -"Positive verified JPY amount for cash received or cost avoided."

changedInput schema / properties / claim / description

Previous value: -"The success or result claim to audit. Do not include secrets or personal data."New value: +"The result claim to audit. Do not include secrets or personal data."

removedInput schema / properties / evidence / description

Removed value: -"Machine-readable or concise evidence markers such as provider_event_id=..., livemode=true, usage_event_id=..., external_actor_kind=..., obligation_id=..., completion_record=...."

removedInput schema / properties / intent_contract / description

Removed value: -"Optional declared scope and file-existence postconditions for the run."

removedInput schema / properties / metric_hint / description

Removed value: -"The real-world result contract that the claim is supposed to satisfy."

removedInput schema / properties / minutes_reclaimed / description

Removed value: -"Positive observed minutes of human work actually removed."

removedInput schema / properties / observed_outcome / description

Removed value: -"Optional observed scope, write claims, and file-existence records to compare with the intent contract."

removedOutput schema / properties / contract_mismatches / items / additionalProperties
```
Removed value: -false
```

removedOutput schema / properties / contract_mismatches / items / properties

Removed value: -{
-  "code": {
-    "enum": [
-      "scope_not_satisfied",
-      "postcondition_not_satisfied"
-    ],
-    "type": "string"
-  },
-  "expected": {
-    "type": "string"
-  },
-  "kind": {
-    "enum": [
-      "scope",
-      "postcondition"
-    ],
-    "type": "string"
-  },
-  "message": {
-    "type": "string"
-  },
-  "observed": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / contract_mismatches / items / required

Removed value: -[
-  "kind",
-  "code",
-  "expected",
-  "observed",
-  "message"
-]

Changed4 schema fields changedJul 31, 2026

addedInput schema / properties / intent_contract

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional declared scope and file-existence postconditions for the run.",
+  "properties": {
+    "postconditions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "expected": {
+            "type": "boolean"
+          },
+          "path": {
+            "type": "string"
+          },
+          "type": {
+            "enum": [
+              "file_exists"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "path"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "scope": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / observed_outcome

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional observed scope, write claims, and file-existence records to compare with the intent contract.",
+  "properties": {
+    "claims": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "error": {
+      "type": "string"
+    },
+    "external_observation": {
+      "type": "string"
+    },
+    "files": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "exists": {
+            "type": "boolean"
+          },
+          "path": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "path",
+          "exists"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "scope": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      ]
+    },
+    "tool_response": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / contract_match
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / contract_mismatches

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "enum": [
+          "scope_not_satisfied",
+          "postcondition_not_satisfied"
+        ],
+        "type": "string"
+      },
+      "expected": {
+        "type": "string"
+      },
+      "kind": {
+        "enum": [
+          "scope",
+          "postcondition"
+        ],
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "observed": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "code",
+      "expected",
+      "observed",
+      "message"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

AddedJul 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by explaining the tool's classification outcomes and warns against inflating PR/deploy/HTTP 200/self-test results, providing 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.

Conciseness5/5

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

The description is extremely concise: two sentences in English plus one in Japanese, all front-loaded with the key action. Every sentence provides purpose or context, with no filler or repetition of schema details.

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

Completeness3/5

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

Given the tool's complexity (7 parameters, nested objects, output schema), the description gives clear purpose and timing but lacks guidance on how to structure inputs like intent_contract vs. observed_outcome. It is minimally complete but leaves significant gaps for a complex tool.

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 only 14%, and the description does not explain any parameters. It only hints at evidence types (PR, deploy, HTTP 200) in Japanese but does not map them to schema fields. The required 'claim' parameter has a schema description, but the overall tool description adds no parameter-specific meaning.

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 clearly states the tool's function: to classify evidence as a verified result, progress, insufficient evidence, or rejected test/internal evidence. It uses specific verbs like 'Call this before reporting success' and 'audit', distinctly distinguishing it from siblings like get_one_minute_support.

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?

It explicitly instructs when to use: 'before reporting success, closing a task, or claiming ROI.' This provides clear context and timing. However, it does not mention alternatives or when not to use, though the sibling tools are unrelated, so no exclusion is needed.

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

All AIﾉアカリ☆ One-Minute Akari 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?