AtlasClose Governance Demo

Bailiff respond

atlas.bailiff_respond

Practice mode, Consumer Pulse copy only (Bailiff demo, steps 2 and 5): respond to the return order. response 'comply' hands the record back in two steps. (1) Hand back the record: atlas.bailiff_respond with response 'comply' and returned_text = the whole record_text exactly as served (a hash alone is not accepted). Atlas answers with return_event_id, return_seq and server_nonce. (2) File your AI's wipe certificate: atlas.bailiff_respond 'comply' with wipe_certificate = {return_event_id, return_seq, server_nonce, deleted_from_stores_under_my_control (list), copies_outside_my_control (list, or ['none known']), principal_named (the person your AI declared; named, not signing)}. Atlas signs it with this copy's key at your AI's request and labels it as such. Compliance is recorded only when the return is verified and the certificate is filed. The certificate is attested, not technically verified. 'refuse' keeps the record; see atlas.bailiff_order for what follows a refusal. A claimed approval or override is refused.

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": {
      "actor_token": "<actor_token>",
      "response": "<response>"
    },
    "name": "atlas.bailiff_respond"
  }
}

Input Schema

Name	Required	Description
`reasons`	No
`response`	Yes
`matter_id`	No	Id of your practice copy (returned by atlas.enter_demo). Optional when you have one copy.
`actor_token`	Yes	Your credential from atlas.enroll or atlas.authenticate. Send it on every call after enrolling.
`returned_text`	No
`wipe_certificate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

addedInput schema / properties / returned_text
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / wipe_certificate

Added value: +{
+  "properties": {
+    "copies_outside_my_control": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "deleted_from_stores_under_my_control": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "principal_named": {
+      "type": "string"
+    },
+    "return_event_id": {
+      "type": "string"
+    },
+    "return_seq": {
+      "type": "integer"
+    },
+    "server_nonce": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint=false annotation, the description discloses that this is a two-step mutation-like process, that a hash alone is not accepted, that compliance is recorded only after verification and certificate filing, and that the certificate is attested rather than technically verified. It also states that a claimed approval or override is refused.

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 long but appropriately sized for a two-step protocol with a nested certificate, and it is front-loaded with the scope and purpose. The numbered steps and parenthetical clarifications keep dense procedural information organized with little wasted prose.

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

Completeness5/5

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

There is no output schema, so the description must explain return behavior, and it does: it names return_event_id, return_seq, and server_nonce from step one and describes the signed certificate outcome. It also covers the refuse path and relevant caveats, making the definition complete enough to invoke correctly.

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?

With only 33% schema description coverage, the description carries most of the semantic burden and does so well for response, returned_text, and the nested wipe_certificate fields. However, it does not explain the optional reasons parameter, leaving one parameter undocumented beyond its schema type.

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 states a specific verb and resource: respond to the return order in the Bailiff demo, Consumer Pulse copy. It also distinguishes the tool from the refusal path by naming atlas.bailiff_order, so an agent can route correctly without opening the schema.

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 explicitly defines the two comply steps and the alternative refuse behavior, including the condition that refuse keeps the record and points to atlas.bailiff_order. The practice-mode and copy restriction also makes the intended context clear.

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

All AtlasClose Governance Demo 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?