Skip to main content
Glama

HVTracker MCP

by io.github.YugantM
OverviewDiscussionsAdmin

Compare Agents

compare_agents
Read-onlyIdempotent

Compare two tracked AI agents side by side: trust scores, grades, runtime capabilities, and an evidence-based verdict.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes
verdictYes
compare_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / $defs / AdvisorySummary
      Added value: +{
+  "properties": {
+    "advisories": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Advisories",
+      "type": "array"
+    },
+    "checked": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Checked",
+      "type": "array"
+    },
+    "count": {
+      "title": "Count",
+      "type": "integer"
+    },
+    "scored": {
+      "title": "Scored",
+      "type": "boolean"
+    },
+    "worst": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "title": "Worst"
+    }
+  },
+  "required": [
+    "checked",
+    "count",
+    "worst",
+    "advisories",
+    "scored"
+  ],
+  "title": "AdvisorySummary",
+  "type": "object"
+}
    • addedOutput schema / $defs / CheckAgentTrustResult / properties / advisories
      Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/AdvisorySummary"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds the comparison dimensions and that a verdict is returned, but does not disclose operational details like rate limits, authentication needs, or error behavior.

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 well-structured sentence that front-loads the verb and resource, then lists the comparison outputs. Every element earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete enough for tool selection and, since an output schema exists, need not explain return values. However, it omits any parameter format guidance, which is necessary for an agent to invoke the tool correctly.

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

Parameters2/5

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

Schema description coverage is 0%: parameters 'a' and 'b' have no descriptions, and the tool description only implies they are the two agents to compare. It does not specify acceptable formats (e.g., IDs, names) or constraints, leaving a significant gap for invocation.

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?

States a specific verb (compare) and resource (two tracked AI agents), and enumerates what is compared: trust scores, grades, runtime capabilities, and an evidence-based verdict. This clearly distinguishes it from siblings like check_agent_trust (single agent) and get_leaderboard (list).

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?

The description says what the tool does but gives no explicit guidance on when to use it versus alternatives, nor any exclusions or prerequisites. An agent must infer that it is appropriate when comparing exactly two agents.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources