Skip to main content
Glama
raditotev

AgentTrust

by raditotev

check_trust_batch

Evaluate trust scores for multiple AI agents in one call, reducing round-trips. Get scores, confidence, and interaction counts for up to 20 agents with a single request.

Instructions

Check trust scores for multiple agents in a single call.

Evaluates up to 20 agents at once, reducing round-trips when you need to assess several potential counterparties before choosing one.

Each agent in the result includes score, confidence, and interaction_count. Agents that don't exist or can't be scored get an inline error.

score_type options: overall, reliability, responsiveness, honesty

Example call: check_trust_batch( agent_ids=["uuid-1", "uuid-2", "uuid-3"], score_type="reliability" )

Example response: { "score_type": "reliability", "results": [ {"agent_id": "uuid-1", "score": 0.82, "confidence": 0.71, "interaction_count": 15}, {"agent_id": "uuid-2", "score": 0.65, "confidence": 0.45, "interaction_count": 7}, {"agent_id": "uuid-3", "error_code": "not_found", "error": "Agent not found"} ], "count": 3, "succeeded": 2, "failed": 1 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idsYes
score_typeNooverall
access_tokenNo
Behavior4/5

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

The description discloses key behaviors: batch limit, result structure (score, confidence, interaction_count), inline errors for missing agents, score_type options, and shows example input/output. However, it omits the role of the access_token parameter, which could affect authorization behavior.

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 and well-structured: purpose first, then constraints, result format, options, and examples. Every sentence adds value without redundancy.

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?

The description covers the tool's purpose, batch limit, error handling, and provides illustrative examples. The missing explanation for access_token is a minor gap, and there is no output schema, but the example response compensates well.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains agent_ids (list of UUIDs) and score_type (with enumerated options), but does not explain the access_token parameter at all. Since the schema has 0% description coverage, the description partially compensates but misses one parameter.

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 trust scores for multiple agents in a single call, with explicit mention of batch size (up to 20) and use case (reducing round-trips). This distinguishes it from single-agent alternatives.

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?

The description explains when to use the tool (assessing several potential counterparties before choosing one) and implies a batch use case. However, it doesn't explicitly compare with sibling tools like check_trust or state when not to use it.

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/raditotev/agent-trust'

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