AtlasClose Governance Demo

Bailiff connector

atlas.bailiff_connector

Practice mode, Consumer Pulse copy only (Bailiff demo, route 7A): get a personal one-time download link (Windows, 30 minutes) and a one-time loan code for the Atlas retrieval connector, which keeps the lent practice data only in folders you name on your own computer. The reply says whether take-back on your computer is on. Demonstration on a synthetic practice matter; not certified; binds only this practice copy.

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>"
    },
    "name": "atlas.bailiff_connector"
  }
}

Input Schema

Name	Required	Description	Default
`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.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond readOnlyHint=false, the description discloses meaningful behavior: the link is personal, single-use and expires in 30 minutes, it is Windows-only, the loan code is one-time, and borrowed data stays in user-named folders. Consistent with the mutation annotation (a code/link is issued), so no contradiction. It omits whether re-calling invalidates prior codes or supersedes an earlier link.

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 constraint is front-loaded, which is good, but the practice/demo/non-certified scope is restated twice (opening clause and closing sentence), and jargon like 'route 7A' and 'take-back' adds length without resolving meaning. Roughly two sentences of content spread across three.

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 credential-issuing tool with only a single annotation and no output schema, the description supplies the operational essentials: expiry, single use, OS constraint, and data residency. The reply is only vaguely characterized ('says whether take-back on your computer is on'), so the return payload remains partly opaque.

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 coverage is 100%, so both matter_id and actor_token are already documented, giving a baseline of 3. The description reinforces the 'practice copy' scoping of matter_id and defines the permitted environment, but adds no syntax, format, or credential-handling detail 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 names a concrete verb and a concrete deliverable: a one-time download link (Windows, 30 minutes) plus a one-time loan code for the Atlas retrieval connector. That is far more specific than a restatement of the title 'Bailiff connector'. It does not explicitly contrast itself with siblings such as atlas.checkout or atlas.external_action, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Scope is stated as a precondition ('Practice mode, Consumer Pulse copy only', 'route 7A'), which implies when the tool applies. However, there is no explicit when-to-use/when-not guidance and no comparison to alternatives an agent might otherwise pick for obtaining artifacts. Usage is inferred from context rather than directed.

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?