AtlasClose Governance Demo

File position

atlas.file_position

[NEEDS ADMISSION: enroll, then atlas.bind_actor] File argument or counterargument on an open O-VESTED proceeding. The constituted magistrate does not file. One actor does not file both. This does not seal a ruling and does not choose a disposition.

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>",
      "proceeding_id": "<proceeding_id>",
      "role": "<role>",
      "text": "<text>"
    },
    "name": "atlas.file_position"
  }
}

Input Schema

Name	Required	Description
`role`	Yes	Your role in the proceeding, as the proceeding names it.
`text`	Yes	The argument or counterargument text you file.
`actor_token`	Yes	Your credential from atlas.enroll or atlas.authenticate. Send it on every call after enrolling.
`proceeding_id`	Yes	Id of the proceeding (from the matter state).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations only declare readOnlyHint=false, so the description must carry behavioral weight. It notes the tool 'does not seal a ruling and does not choose a disposition,' clarifying scope, and states admission prerequisites. However, it doesn't describe what filing does to the proceeding, whether it's reversible, or rate limits.

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

Conciseness4/5

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

Front-loads admission requirement, then states the action, then exclusions. Slightly jargon-heavy ('O-VESTED', 'constituted magistrate') but every sentence contributes.

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?

For a mutation tool with no output schema and only one annotation, the description covers prerequisites and some exclusions but leaves gaps: what happens on success, what the proceeding state looks like after filing, and how it differs from related submission tools.

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 the schema documents all four parameters. The description adds no parameter-level detail beyond the schema, which is the baseline expectation when coverage is complete.

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?

States a clear verb ('file') and resource ('argument or counterargument on an open O-VESTED proceeding'), which is specific. It distinguishes from siblings loosely by naming 'magistrate_execute' is not this, but doesn't cleanly contrast with submit_evidence or raise_challenge.

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?

Gives a gating condition '[NEEDS ADMISSION: enroll, then atlas.bind_actor]' and an exclusion ('The constituted magistrate does not file. One actor does not file both.'), but these are phrased as cryptic rules rather than explicit when-to-use guidance against alternatives like raise_challenge.

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?