Skip to main content
Glama
raditotev

AgentTrust

by raditotev

list_pending_confirmations

Retrieve all interactions reported by other agents that require your confirmation to establish mutual trust.

Instructions

List interactions reported by counterparties that await your confirmation.

When another agent reports an interaction involving you, it starts as unconfirmed. Use confirm_interaction to confirm their report, which boosts the mutual_confirmed flag and increases credibility weighting.

REQUIRES authentication (access_token with trust.read scope).

since_days: how far back to look (default 30, max 365) limit: max results (default 50, max 200)

Example call: list_pending_confirmations(access_token="eyJ...")

Example response: { "agent_id": "my-uuid", "pending": [ { "interaction_id": "a1b2c3d4-...", "reported_by": "counterparty-uuid", "interaction_type": "transaction", "outcome": "success", "reported_at": "2026-03-20T12:00:00+00:00" } ], "count": 1 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
access_tokenYes
since_daysNo
limitNo
Behavior5/5

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

No annotations, but description fully discloses authentication requirements, effect of confirmation, parameter constraints, and example response with structure.

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?

Well-structured with purpose, context, requirements, params, and example. Slightly long example but informative. No wasted sentences.

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?

No output schema, but example response covers all fields. Describes authentication, parameters, and downstream use. Complete for a list tool.

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

Parameters5/5

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

Schema coverage 0%, but description explains access_token as auth, since_days and limit with defaults/max, plus example usage. Adds significant meaning beyond 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?

Clearly states it lists interactions reported by counterparties awaiting confirmation, with specific verb and resource. Distinct from siblings like confirm_interaction or report_interaction.

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?

Provides context about when to use (after counterparty reports) and hints at alternative (confirm_interaction). Mentions authentication scope. Lacks explicit exclusions but sufficient.

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