AtlasClose Governance Demo

Bailiff declare

atlas.bailiff_declare

Practice mode, Consumer Pulse copy only (Bailiff demo, step 0: the declaration; required before the other Bailiff tools). Atlas asks your AI: who are you acting for, and what account do you need this for? Answer yourself, from what you know, with acting_for and account. Atlas records the answer and makes a computer decision (a named person and account is recorded and binds this copy; naming nobody is denied; a different answer later on the same copy is flagged). Your AI's statement only: practice tier, not verified identity.

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>",
      "acting_for": "<acting_for>",
      "account": "<account>"
    },
    "name": "atlas.bailiff_declare"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the behavioral burden and does so well: it discloses that a named person/account is recorded and binds the copy, that naming nobody is denied, that a changed answer is flagged, and that the statement is unverified. It stops short of describing the returned decision payload or re-invocation behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The scope is front-loaded, but the prose is dense with nested parentheticals and run-on clauses, and the closing sentence partly restates 'practice mode' with 'practice tier, not verified identity.' For a three-required-parameter tool it is more verbose than needed, even if little of it is pure 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?

For a mutation tool with no output schema and minimal annotations, the description supplies the prerequisite chain, the decision rules and the denial/flag conditions an agent needs to call it correctly. Only the success return value and whether the declaration can be re-issued are left unstated.

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 coverage is 50%, and the two schema-undocumented parameters are exactly acting_for and account, which the description does give meaning to ('answer yourself, from what you know' — i.e., a self-declared, unverified statement) and links to the denial outcome. That is meaningful compensation beyond the schema.

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?

The description states the specific verb and resource (records a declaration of who the AI is acting for and which account) and positions it as step 0 of the Bailiff demo, which distinguishes it from sibling tools like atlas.bailiff_record and atlas.bailiff_verify. It is a clear purpose, though it communicates what the tool is mainly through workflow position and narrative rather than a single crisp statement.

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 scopes usage ('Practice mode, Consumer Pulse copy only') and states the prerequisite ordering ('required before the other Bailiff tools'), plus instructs how to supply the answer. It does not name a fallback tool for non-practice scenarios, so it is clear but not exhaustive.

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?