Skip to main content
Glama
alexfleetcommander

Agent Trust Stack MCP Server

by alexfleetcommander
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

arp_check

Check an agent's reputation score by retrieving aggregated data including average score, rating count, score range, and unique raters. Assess trustworthiness and accountability.

Instructions

Check an agent's reputation score.

Retrieves aggregated reputation data for the specified agent, including
average score, rating count, score range, and unique rater count.

Args:
    agent_id: ID of the agent to check reputation for

Returns:
    JSON with rating_count, average_score, min/max scores, unique_raters,
    and first/latest rating timestamps

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It explicitly states it retrieves data (read-only) and lists return fields, providing good transparency for a simple read operation.

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?

The description is concise with no wasted words. It front-loads the purpose, then clearly lists parameters and return fields in a structured manner.

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?

Given the tool's simplicity and the presence of an output schema (implied), the description covers purpose, parameter, and return fields adequately. Missing error handling or prerequisites, but acceptable for this context.

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 0%, so the description provides necessary meaning for the agent_id parameter: 'ID of the agent to check reputation for'. This adds value beyond the bare 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?

The description clearly states the tool checks an agent's reputation score, listing specific return fields. It distinguishes itself from siblings like arp_rate (likely for rating) and coc_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. The description only explains what it does, not when it's appropriate to choose it over siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexfleetcommander/agent-trust-stack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server