Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

repo_verdict

Paid $0.02 (x402, USDC Base): one-line GO / CAUTION / HONEYPOT_RISK verdict for a repo. Impulse-priced pre-flight check.

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": {
      "repo": "<repo>"
    },
    "name": "repo_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesowner/name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 disclosure burden. It usefully states the paid cost, payment rail (x402, USDC Base), and the returned verdict categories, but it does not explain verdict criteria, data sources, latency, failure modes, or whether payment is per call.

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?

The description is two compact, front-loaded fragments covering cost, output, and intended use. There is no filler or repetition, and every element contributes to rapid tool selection.

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 paid verdict tool with no output schema, the description covers cost, payment rail, and the exact verdict labels. It is adequate for invocation, though it would be stronger with explicit comparison to score_repo_trust and a brief note on what drives the verdict.

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 100% and the schema defines repo as owner/name. The description only says 'for a repo' and adds no syntax, constraints, or examples beyond the schema, so the baseline of 3 is appropriate.

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 states a specific resource (repo) and a specific output (one-line GO / CAUTION / HONEYPOT_RISK verdict), so the tool's purpose is clear. It distinguishes itself from token-verdict siblings by repo focus, but it does not explicitly differentiate from score_repo_trust.

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?

The phrase 'Impulse-priced pre-flight check' implies when to use it: a quick, low-cost assessment before acting on a repo. However, it names no alternatives or when-not-to-use conditions, especially relative to sibling score_repo_trust.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources