Skip to main content
Glama

check_trust

Determine if an agent meets a minimum trust tier for delegation. Returns a yes/no verdict with reason, helping decide whether to assign a task.

Instructions

Quick yes/no delegation decision: is this agent trusted enough for my task?

Returns allowed (true/false) with a human-readable reason. Use this when you
only need a go/no-go answer before delegating work.

NOT for detailed analysis — use check_reputation for full score breakdown.
NOT for rating history — use get_attestations_received for peer reviews.

Tiers from lowest to highest: newcomer, basic, trusted, elite.
Advisory signal, not a guarantee.

Read-only. Does not modify any data.

Args:
    did: Agent's DID (did:key:z6Mk...).
    min_tier: Minimum required tier: "newcomer", "basic", "trusted", "elite". Default "trusted".
    task_type: Optional task category for specialized scoring.

Returns:
    JSON with allowed (true/false), score, tier, risk_level, and reason.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
didYesAgent's DID to evaluate. Format: did:key:z6Mk...
min_tierNoMinimum required trust tier. One of: newcomer, basic, trusted, elite. Default: trustedtrusted
task_typeNoOptional task category for specialized scoring. Examples: code_quality, task_completion, data_accuracy

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden and clearly states 'Read-only. Does not modify any data' and 'Advisory signal, not a guarantee.' Some additional context like authentication requirements or caching could improve, but it is sufficient.

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?

Description is concise, well-structured with bullet points, and front-loaded with the primary purpose. Every sentence adds value with no 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 presence of an output schema listing fields, the description adequately covers return values plus usage context. The tool is simple, and the description covers what an agent needs to invoke it correctly.

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?

Input schema has 100% description coverage; the description adds context by explaining tier order and providing examples for task_type. While the schema already covers the parameters, the description provides helpful elaboration.

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 the tool is for quick yes/no delegation decisions, distinguishing it from siblings like check_reputation and get_attestations_received. The verb 'check' and resource 'trust' are specific and the scope is well-defined.

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?

Explicitly provides when to use (quick go/no-go before delegating) and when not to (NOT for detailed analysis or rating history), with specific alternatives mentioned. Also explains the tier system and advisory nature.

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/agentveil-protocol/avp-sdk'

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