Skip to main content
Glama
Sign In
trust-mcp

trust-mcp

by BillyTheManBot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

trust_list

View all registered agents and their trust scores. Paginate to browse and verify trust before transacting.

Instructions

List all registered agents with their trust scores. Supports pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trust_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
limitNoMax agents to return (default 20, max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses a read-only behavior ('List') and adds 'Supports pagination', which is useful. However, it omits details about return format, sorting, or error behavior, which would be helpful for a complete behavioral picture.

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 two concise sentences, front-loaded with the key action and scope, with no filler or wasted words.

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?

For a simple paginated listing tool with two well-documented parameters and no output schema, this description is fairly complete. It covers the action, scope, content, and pagination, though it could benefit from mentioning sorting or default return format.

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 coverage is 100% for both parameters (page, limit), so the baseline is 3. The description only reiterates pagination without adding new meaning beyond what the schema already provides.

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 uses the specific verb 'List' with a clear resource ('all registered agents') and content ('their trust scores'). The phrase 'all registered agents' clearly distinguishes this from siblings like trust_lookup (likely single-agent lookup) and trust_search (filtered search), making the purpose unambiguous.

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

Usage Guidelines3/5

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

The description implies the tool is used for listing all registered agents, but it does not explicitly state when to choose it over alternatives like trust_search or trust_lookup, nor does it provide any exclusions or context.

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

Deploy Server

Other Tools