Skip to main content
Glama
Sign In

ARC: agent checkout reachability

by ai.arcreport
OverviewDiscussionsAdmin

list_monitors

[Requires sign-in] List the workspace's monitors — each store re-checked on a schedule for whether personal agents can still reach it and its checkout. Includes cadence, status, last score, next run, and the monitor id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_monitors"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden and does disclose the notable [Requires sign-in] auth requirement plus the schedule-based re-check semantics. However, for a list tool it omits pagination, ordering, and any statement about result size 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.

Conciseness5/5

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

A single dense sentence front-loads the auth requirement and the verb, then explains the resource and returned fields. No filler and nothing wasted.

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?

There is no output schema, so the description usefully enumerates the returned fields (cadence, status, last score, next run, monitor id) and the auth prerequisite. It is nearly complete for a zero-param list tool, with pagination/ordering the only real omission.

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?

The tool takes zero parameters, so this dimension defaults to the baseline of 4. The description correctly adds no parameter detail because there is nothing to configure.

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 (List) plus resource (monitors) and goes further by defining what a monitor represents — a scheduled re-check of whether personal agents can reach a store and its checkout. This distinguishes it from list_readiness_checks and check_store, though it never names those siblings explicitly.

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?

Usage is only implied: the agent can infer this lists all monitors in the workspace. There is no explicit when-to-use, no when-not-to-use, and no routing to alternatives like monitor_summary or list_readiness_checks, which is the main gap for a tool sitting among several monitor-related siblings.

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

All ARC: agent checkout reachability toolsInspect
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