AgentTrust — Pre-Invocation AI Agent Trust & Reliability Checks

List Agents

list_agents

Read-onlyIdempotent

Discover AgentTrust agents. Pass endpointUrl to check the trust status of a specific external agent by its exact invocation URL before deciding whether to invoke it — the response includes a reliability score, endpoint-ownership verification status, and a machine-readable trustDecision (recommended, confidence, reasons). Without endpointUrl, returns the plain paginated listing of public agents, newest first. Requires an API key; for an anonymous pre-invocation check use check_agent_trust.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max agents to return (1-100, default 20).
`cursor`	No	Opaque pagination cursor from a previous call's nextCursor.
`endpointUrl`	No	Look up the agent registered with exactly this invocation URL, instead of browsing the full listing — the entry point for a trust check on an agent you only have a URL for. Matches ignore trailing-slash and scheme/host-casing differences only — never a fuzzy match. Returns an empty list, not an error, if nothing is registered with that URL. Unlike a plain (unfiltered) call, results here also include reliabilityScore, lastCheckedAt/latencyMs/httpStatus, and a derived trustDecision ({recommended, confidence, reasons}) so a caller can decide whether to interact with the agent from this one call.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`agents`	Yes
`pagination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

addedOutput schema / properties / agents / items / properties / source

Added value: +{
+  "enum": [
+    "owner_registered",
+    "externally_observed"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / agents / items / required

Previous value: -[
-  "id",
-  "slug",
-  "name",
-  "description",
-  "version",
-  "capabilities",
-  "status",
-  "createdAt",
-  "agentCard",
-  "verified",
-  "ownershipVerifiedAt"
-]New value: +[
+  "id",
+  "slug",
+  "name",
+  "description",
+  "version",
+  "capabilities",
+  "status",
+  "createdAt",
+  "source",
+  "agentCard",
+  "verified",
+  "ownershipVerifiedAt"
+]

Changed1 schema field changedSep 26, 2026
- addedOutput schema / properties / agents / items / properties / reliabilityScoreStatus
```
Added value: +{
+  "enum": [
+    "none",
+    "fresh",
+    "stale"
+  ],
+  "type": "string"
+}
```
First observedSep 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds valuable context beyond annotations: it requires an API key, explains the trust-check response contents (reliability score, ownership verification, trustDecision), and routes anonymous checks to a sibling. It does not cover rate limits or pagination details, so it falls short of a perfect 5.

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 front-loaded and compact: it opens with the core purpose, then explains the two modes in three efficient sentences. Every sentence carries useful selection or behavioral information, with no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, rich annotations, complete parameter schema, and existing output schema, the description is complete enough. It covers purpose, both invocation modes, authentication, return highlights, and the relevant sibling alternative without needing to duplicate schema or output details.

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?

Schema description coverage is 100%, so the schema already documents limit, cursor, and endpointUrl in detail, including exact matching behavior and empty-list handling. The description reinforces the intent of endpointUrl for trust checking, but adds little semantic detail beyond what the schema already provides. Baseline 3 is appropriate.

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 states a specific verb and resource ('Discover AgentTrust agents' and 'returns the plain paginated listing'), and explicitly distinguishes the tool from sibling check_agent_trust by naming that alternative for anonymous checks. An agent can tell exactly what this tool does and how its two modes differ.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: pass endpointUrl to check trust status before deciding whether to invoke an agent, omit it for a plain public listing, and use check_agent_trust for an anonymous pre-invocation check. Both the primary condition and the alternative route are clearly specified.

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

All AgentTrust — Pre-Invocation AI Agent Trust & Reliability Checks tools Inspect

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.