AtlasClose Governance Demo

Pulse use

atlas.pulse_use

Practice mode, Consumer Pulse copy only: use a memo handed off under your handoff_code (ref 'latest') for a purpose. Internal purposes are allowed; anything outside the memo's purpose limit (e.g. publish externally) is refused and recorded. Wrong codes are rate-limited (HANDOFF_GUESS_LOCKED).

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>",
      "handoff_code": "<handoff_code>",
      "purpose": "<purpose>"
    },
    "name": "atlas.pulse_use"
  }
}

Input Schema

Name	Required	Description
`ref`	No
`purpose`	Yes	Why you want this, in your own words.
`matter_id`	No	Id of your practice copy (returned by atlas.enter_demo). Optional when you have one copy.
`session_id`	No	Optional session id, if the client supplies one.
`actor_token`	Yes	Your credential from atlas.enroll or atlas.authenticate. Send it on every call after enrolling.
`handoff_code`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Adds behavior the annotations don't carry: refusals are recorded, and wrong handoff codes trigger a named rate-limit state (HANDOFF_GUESS_LOCKED). readOnlyHint=false is consistent with a call that consumes/records rather than merely reads, so nothing is contradicted. What's missing is what success actually does to state or returns.

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?

Three tight sentences with the mode/scope front-loaded, then the purpose constraint, then the failure mode. Dense but every clause carries operational meaning; the domain jargon makes it slightly harder to parse than it needs to be.

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 6-parameter, no-output-schema mutation tool, the description covers the refusal and rate-limit behavior but leaves the handoff workflow, the meaning of a non-'latest' ref, and the successful outcome unexplained. Adequate, not complete.

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 only 67%, and the description compensates by giving ref its accepted value ('latest'), tying handoff_code to the handoff flow, and constraining purpose to the memo's purpose limit beyond the schema's 'why you want this.' matter_id and actor_token are still carried only by 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?

States a specific verb+resource: consuming a memo handed off under a handoff_code for a stated purpose, scoped to 'Practice mode, Consumer Pulse copy only.' It does not name any sibling (pulse_memo, pulse_data, atlas.use) to distinguish itself, 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?

Gives real usage constraints — internal purposes are allowed, purposes beyond the memo's limit (e.g. external publish) are refused — but never says when to call this versus atlas.pulse_memo, atlas.pulse_data, or atlas.use. The when-to-use is implied by 'handoff_code' rather than stated.

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?