Skip to main content
Glama
Sign In

Moatlight

by com.moatlight
OverviewDiscussionsAdmin

Run an agent readiness scan (Early Access pass)

scan_agent_readiness

Runs, or reuses a result under 24 hours old, for the report's website. Set force to true to scan again after fixing something. Rate limited. Needs login with scope agent-readiness:scan.

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": {
      "reportId": "<reportId>"
    },
    "name": "scan_agent_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoScan again even if a recent result exists.
reportIdYesReport id from POST /api/v1/reports or GET /api/v1/reports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare the non-read-only, non-destructive, closed-world profile; the description adds real operational detail beyond them: a 24-hour result cache, a rate limit, and a required login scope (agent-readiness:scan). It does not say what happens on scan failure or how long a fresh scan takes, which keeps it below a 5.

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 short sentences, front-loaded with the core action, and each one carries distinct information (cache behavior, force semantics, access constraints). The first sentence's word order is slightly tangled but nothing is 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?

For a two-parameter tool with no output schema and full schema coverage, the description covers what an agent needs: cache behavior, the force override, rate limiting, and the auth scope. Return shape is unspecified, which is a minor gap since no output schema exists.

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 genuinely adds meaning: the 24-hour recency threshold that defines 'recent result' and the 'after fixing something' framing for force. The reportId parameter is left entirely to the schema, which already documents its source endpoints.

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 names a specific verb (scan) and resource (the report's agent readiness for its website), which differentiates it from the sibling read tool get_agent_readiness. The opening clause is grammatically awkward ('Runs, or reuses a result under 24 hours old, for the report's website') but the intent is still recoverable.

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 clearly states the default behavior (reuse a result under 24 hours old) and the condition for forcing a fresh run ('set force to true to scan again after fixing something'). It stops short of naming an alternative tool or stating when not to call it, so it is clear context without explicit exclusions.

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

All Moatlight 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