Atlasemoji

Verify an Atlas Agent Connection

verify_atlas_agent

Idempotent

Complete proof of life for an already configured Atlas Agent MCP connection. The authenticated MCP principal must be authorized for the requested company and for this tool. Atlas verifies that the connection belongs to the requested Agent and records the current Manifest revision before returning a sanitized Connection Card.

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": {
      "companyId": "<companyId>",
      "agentId": "<agentId>",
      "connectionId": "<connectionId>"
    },
    "name": "verify_atlas_agent"
  }
}

Input Schema

Name	Required	Description	Default
`agentId`	Yes
`companyId`	Yes
`connectionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations mark this as non-read-only but idempotent and non-destructive; the description explains why by disclosing that the tool 'records the current Manifest revision' as a side effect, plus the authorization requirement and a sanitized return. This adds real behavioral context beyond the hint flags, though it doesn't detail failure modes or what 'sanitized' removes.

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?

Two tight sentences with the core purpose and the side effect front-loaded before the return value. No filler, though the second sentence is dense with authorization and behavior clauses.

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?

With no output schema, the description carries the return-value burden and does so by naming the Connection Card result. It covers prerequisites and side effects; only parameter-level detail and error behavior are missing.

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 0%, so the three identifiers are undocumented in structured fields. The description implicitly maps the three parameters (company, agent, connection) to their entities, but adds no format, origin, or lookup guidance to compensate for the coverage gap.

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 a specific action on a specific resource: it proves that an already configured Atlas Agent MCP connection is live, confirms ownership by the requested Agent, and returns a Connection Card. That is clearly distinguishable from siblings like get_atlas_profile or validate_manifest_schema, though it never names an alternative directly.

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 scopes usage to 'an already configured' connection and states the authorization prerequisites (principal must be authorized for the company and for this tool). It gives clear context for when the tool applies, but offers no explicit exclusions or named alternative tools.

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

All Atlasemoji 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?