Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

score_repo_trust

Paid $0.10 (x402, USDC Base): trust score 0-100 + GO/CAUTION/HONEYPOT_RISK verdict + reasons for a GitHub repo. Screen bounties before working them — one avoided rug pays for 1000 calls.

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": "score_repo_trust"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesowner/name, e.g. facebook/react

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the most decision-critical trait: it is a paid call ($0.10 via x402 in USDC on Base). That payment/auth requirement is exactly the kind of context annotations would normally supply. Remaining gaps are error behavior for nonexistent repos, latency, and caching, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Effectively one sentence, front-loaded with the price the agent must mentally budget before calling. The closing 'one avoided rug pays for 1000 calls' is promotional framing but does reinforce the cost/benefit decision. Slightly dense, but nothing is padded.

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 tool with no output schema, the description usefully enumerates the return payload (score, verdict, reasons), so the agent knows what comes back. What is missing is sibling disambiguation against repo_verdict, which matters given how similar the names are.

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 parameter and schema description coverage is 100%, with the schema itself showing the 'owner/name' format and an example. The description adds no parsing or format meaning beyond that, so the schema does all the work and the baseline 3 applies.

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?

States a specific verb+resource: produces a trust score (0-100), a GO/CAUTION/HONEYPOT_RISK verdict, and reasons for a GitHub repo. The output shape is concrete enough that an agent knows what it gets back. It stops short of 5 because the sibling 'repo_verdict' sounds nearly identical and the description never draws the line between them.

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?

Gives one concrete usage scenario — screen bounties before working them — which implies the trigger context. There is no when-not guidance, no prerequisite statement, and no mention of how this differs from repo_verdict or get_token_verdict, leaving the agent to guess between close siblings.

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