Argus Console — AI Agent Test Lab

argus_verify_agent

Verify ownership of an agent endpoint before it can be registered in Argus Console: checks that the verify token is served at https:///.well-known/argus-verify.txt. Run once per endpoint, right after the user adds the agent in Argus Console and shares the verify token. Does not consume any quota.

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": {
      "endpoint": "<endpoint>",
      "token": "<token>"
    },
    "name": "argus_verify_agent"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes	Verify token from Argus Console → Agents
`endpoint`	Yes	Public base URL of the agent, e.g. https://my-agent.replit.dev

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it reveals that the tool performs an outbound fetch of a well-known URL, that it is a gating prerequisite to registration rather than the registration itself, and that it has no quota cost. It does not say what is returned on success/failure or what happens on retry, which for a network-dependent check would matter.

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

Conciseness5/5

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

Two sentences, both front-loaded with the essential information: purpose and mechanism first, then timing and cost. No filler, no repetition of the schema.

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 two-parameter, no-annotation, no-output-schema tool the description covers purpose, timing, mechanism, and cost. The remaining gap is the response shape (pass/fail fields, error messages), which an agent cannot infer from any structured field since there is no output schema.

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 100%, so the baseline is 3, but the description adds real meaning by showing how the two parameters combine — the endpoint is the base host under which /.well-known/argus-verify.txt is fetched, and the token content must match what is served there. That relationship is not expressed in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Verify ownership of an agent endpoint') and adds the exact mechanism: checking that the token is served at https://<endpoint>/.well-known/argus-verify.txt. This is clearly distinct from every sibling (list_agents, run_engine, run_simulation, get_run_report), which are registry-query and execution tools.

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?

Provides a precise trigger and ordering: run once per endpoint, right after the user adds the agent in Argus Console and shares the verify token, and before registration. It also rules out cost concerns ('does not consume any quota'). It stops short of stating when NOT to run (e.g., re-verifying an already-verified endpoint), leaving a small gap.

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

All Argus Console — AI Agent Test Lab 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.