Skip to main content
Glama
YugantM

io.github.yugantm/hvtracker-mcp

by YugantM

Check Agent Trust

check_agent_trust
Read-onlyIdempotent

Verify the trust profile of any AI agent or framework by retrieving its runtime capabilities and offline-verifiable Ed25519-signed credential URL.

Instructions

Get the HVTracker trust profile for a tracked AI agent or framework, including its runtime capability surface and the URL of its Ed25519-signed trust credential (verifiable offline).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
name_or_repoYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations provide readOnlyHint, idempotentHint, openWorldHint, destructiveHint. Description adds context about what the trust profile includes but does not disclose additional behavioral traits beyond the annotations.

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?

Single sentence, front-loaded, no redundant phrasing. Every word adds value.

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?

Given low complexity (1 param) and presence of output schema, description covers main return elements. Lacks parameter guidance but otherwise complete.

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

Parameters1/5

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

Single parameter 'name_or_repo' lacks description. With 0% schema description coverage, the description should clarify this parameter but does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states that it retrieves a trust profile for an AI agent or framework, including specific elements (runtime capability surface and Ed25519-signed trust credential). Distinguishes from siblings via specificity but does not explicitly differentiate.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like compare_agents or search_agents. Missing context on prerequisites or scenarios.

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/YugantM/hvtracker-mcp'

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