Skip to main content
Glama
aos-standard

MCP Agent Health Reporter

by aos-standard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
aos_agent_health_scanA
Scan a single AOS agent by tool_id under target_dir and return health score.

Args:
    tool_id: Four-digit agent id (e.g. "1066").
    target_dir: Root directory to search (default: cwd or AOS_HEALTH_TARGET_DIR).
    mock: Deterministic mock output for CI (no filesystem reads).
aos_agent_health_audit
Audit all agents under target_dir and return aggregate health report.

Args:
    target_dir: Root directory to search (default: cwd or AOS_HEALTH_TARGET_DIR).
    mock: Deterministic mock output for CI.
aos_agent_health_self_testC

Self-connectivity check — returns sample scan JSON for MCP wiring verification.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

B3.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one performs a health scan on a specific agent, the other is a self-connectivity check. No overlap or ambiguity.

Naming Consistency5/5

Both tools follow the consistent pattern 'aos_agent_health_<verb>', using snake_case and clear verb descriptors ('scan' and 'self_test').

Tool Count3/5

Two tools is minimal but acceptable for a focused health reporter. However, the server's scope feels limited, bordering on thin.

Completeness2/5

Missing obvious operations like listing agents, batch scanning, or retrieving historic results. The surface covers only one core action and a connectivity test, leaving significant gaps.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources