Skip to main content
Glama

HVTracker MCP

by io.github.YugantM

Check Agent Trust

check_agent_trust
Read-onlyIdempotent

Get the HVTracker supply-chain trust profile for a tracked AI agent or framework.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
name_or_repoYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
rankNo
repoNo
queryYes
messageNo
trackedYes
categoryNo
submit_urlNo
profile_urlNo
trust_scoreNo
capabilitiesNo
coverage_gradeNo
credential_urlNo
evidence_gradeNo
has_provenanceNo
scorecard_scoreNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • addedOutput schema / $defs
      Added value: +{
+  "Capabilities": {
+    "properties": {
+      "drift_status": {
+        "title": "Drift Status",
+        "type": "string"
+      },
+      "mcp_status": {
+        "title": "Mcp Status",
+        "type": "string"
+      },
+      "plugin_system": {
+        "title": "Plugin System",
+        "type": "string"
+      },
+      "provider_count": {
+        "title": "Provider Count",
+        "type": "integer"
+      },
+      "requires_api_keys": {
+        "title": "Requires Api Keys",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "mcp_status",
+      "provider_count",
+      "requires_api_keys",
+      "plugin_system",
+      "drift_status"
+    ],
+    "title": "Capabilities",
+    "type": "object"
+  }
+}
    • addedOutput schema / properties / capabilities
      Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/Capabilities"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedOutput schema / properties / coverage_grade
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Coverage Grade"
+}
    • addedOutput schema / properties / credential_url
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Credential Url"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Category"
+    },
+    "evidence_grade": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Evidence Grade"
+    },
+    "has_provenance": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Has Provenance"
+    },
+    "message": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Message"
+    },
+    "name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Name"
+    },
+    "profile_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Profile Url"
+    },
+    "query": {
+      "title": "Query",
+      "type": "string"
+    },
+    "rank": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Rank"
+    },
+    "repo": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Repo"
+    },
+    "scorecard_score": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Scorecard Score"
+    },
+    "submit_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Submit Url"
+    },
+    "tracked": {
+      "title": "Tracked",
+      "type": "boolean"
+    },
+    "trust_score": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Trust Score"
+    }
+  },
+  "required": [
+    "query",
+    "tracked"
+  ],
+  "title": "CheckAgentTrustResult",
+  "type": "object"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds minimal behavioral context beyond 'Get... trust profile'. It does not disclose potential errors, permissions, or data freshness. With annotations covering safety, a 3 is appropriate.

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?

A single sentence without unnecessary words. Efficiently communicates the tool's purpose. No structural improvements needed.

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?

The tool has one input parameter and an output schema exists. The description combined with annotations and schema provides basic context for a simple tool. It could mention what the trust profile includes, but the output schema presumably covers that, so completeness is adequate.

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 0%, so the description must compensate. The tool description implies the parameter is a name or repository identifier, adding some context. However, it lacks format, examples, or constraints. Baseline 3 is fair.

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?

The description clearly states the tool retrieves the HVTracker supply-chain trust profile for a specific agent or framework. It distinguishes from siblings like search_agents or get_agent_history by focusing on trust profile retrieval. However, it could more explicitly differentiate itself.

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 vs sibling tools. No mention of prerequisites or context where this tool is appropriate. The description only states what it does, not when or why to choose it.

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

All HVTracker MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose: agent trust profile, comparison, history, leaderboard, categories, bulk scan, search, and MCP server verification. No overlap in functionality.

Naming Consistency5/5

All tools use consistent snake_case and verb_noun pattern (e.g., check_agent_trust, verify_mcp_server). No mixing of conventions.

Tool Count5/5

8 tools is well-scoped for a trust-tracking server, covering individual checks, comparisons, history, bulk scanning, and discovery without excess.

Completeness5/5

The tool surface covers all primary use cases: single agent lookups, comparisons, historical trends, leaderboards, category browsing, bulk scanning, and specific MCP server checks. No obvious gaps.

Resources