Skip to main content
Glama

trustgate

Run a credit-style trust check on an AI agent to get APPROVED, CAUTION, or DENIED with its trust score, security grade, and risk factors before relying on it.

Instructions

Credit check an agent. Returns APPROVED, CAUTION, or DENIED with trust score, security grade, and risk factors. Like a credit score but for AI agents.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYesAgent name to credit-check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the return vocabulary and result components, which is the most important behavioral fact. It says nothing about whether the call is read-only or registers an unknown agent, what happens when the name is unrecognized, whether results are cached, or any rate/cost limits.

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?

Three short sentences: purpose first, outputs second, analogy last as a framing aid. Nothing is repeated and nothing is padding; the front-loaded structure means an agent can decide from the first clause.

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 one-parameter lookup with no output schema, the description covers purpose and return values adequately, so an agent can call it correctly. The remaining gap is edge-case behavior for unknown agent names and the relationship to lookalike siblings, which matters given the crowded namespace but is not essential to make the call.

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?

There is a single required parameter whose schema description is 100% covered ('Agent name to credit-check'), so the schema already does the documentation work. The description adds no extra semantics about name format, aliases, or how an unknown name is resolved, which is the correct baseline of 3 for full schema coverage.

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 gives a specific verb and resource ('Credit check an agent') and states the exact outputs (APPROVED, CAUTION, DENIED plus trust score, security grade, risk factors), so an agent knows precisely what the tool does. It does not, however, distinguish itself from the similarly named sibling 'check_agent' or 'trustgate'-adjacent tools like 'security_scan', leaving overlap ambiguity.

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?

'Like a credit score but for AI agents' implicitly frames the use case as pre-interaction trust assessment, which is enough to infer when to call it. There is no explicit when-not-to-use guidance, no mention of how it differs from 'check_agent' or 'security_scan', and no prerequisites or exclusions stated.

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