Skip to main content
Glama

Ravi CI Guard: GitHub Actions security audit

Redeem a transfer for a pass (free)

redeem_transfer_pass
Read-only

FREE. After sending USDC on Base to the address in payment_options, give the transaction hash to get your CI Guard pass token (and the Team Kit download link for 3 USDC or more). Redeeming the same hash again returns the same token.

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": {
      "tx": "<tx>"
    },
    "name": "redeem_transfer_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYes0x-prefixed transaction hash of your USDC transfer on Base

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Adds real behavior beyond the annotations: it is free, redemption is idempotent (same hash returns the same token), and the 3 USDC threshold unlocks the Team Kit link. It does not say what happens on an invalid or unknown hash, how long confirmation takes, or what the success payload looks like. The 'get your pass token' framing is idempotent and non-mutating, so it is consistent with readOnlyHint=true rather than contradicting it.

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?

Two short sentences, front-loaded with the free/idempotent facts and the prerequisite address source. Nothing is padded and no sentence restates the tool name.

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?

With no output schema, the description does carry the burden of describing returns, and it names both the pass token and the conditional Team Kit link. It is complete enough to call correctly, though it omits failure modes and the response shape for an invalid hash.

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

Parameters4/5

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

Schema coverage is 100% and there is only one parameter, so the baseline is met by the schema alone. The description still adds the chain constraint (Base) and ties the value to a prior transfer, which clarifies what the hash must represent.

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 and outcome (redeem a transfer to get a CI Guard pass token) and anchors it to a concrete prerequisite tool, payment_options. An agent can distinguish this from payment_options or audit_* siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear precondition and ordering: send USDC on Base to the address from payment_options first, then call this with the tx hash. It lacks an explicit 'when not to use' clause or error routing (e.g. what to do if the hash is invalid or the amount is short), so it stops short of full when/when-not guidance.

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