Skip to main content
Glama

UAI x402 Security Tools

repo-security-bundle

Combined repo security scan — secret scan, GitHub Actions workflow exposure check, and dependency manifest CVE review in one agent call for CI pre-commit and supply-chain triage. (REST equivalent: POST /api/v1/repo-security-bundle, $0.04)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "repo-security-bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoOptional text/config to scan for secrets
manifestTextNoOptional package.json or lockfile contents
workflowYamlNoOptional GitHub Actions workflow YAML

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?

Annotations carry only a title, so the description bears the full behavioral burden. It does add genuinely useful context that structured fields lack — the $0.04 cost and the REST endpoint equivalent — but it never states that the operation is read-only, what authentication or rate limits apply, or what the combined findings look like.

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?

A single dense sentence front-loads the composite nature of the scan, with the REST/cost detail parenthesized as secondary. No sentence is wasted, though the parenthetical is metadata rather than guidance an agent needs to invoke the tool.

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?

There is no output schema, so return values need not be explained, but the description leaves a material ambiguity: all three parameters are optional and no repository reference exists, so an agent cannot tell from the definition what is actually scanned when fields are omitted or whether empty input is valid. For a bundled scanner this is a meaningful hole.

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 coverage is 100% and each optional field is already documented in the schema, so the baseline of 3 applies. The description adds nothing about how the three inputs feed the three constituent scans, and notably does not clarify that the caller supplies raw content blobs rather than a repository identifier — a point an agent could easily misread from the name 'repo-security-bundle'.

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 names a specific composite operation and enumerates its three constituent scans (secret scan, GitHub Actions workflow exposure, dependency manifest CVE review), which clearly separates it from single-purpose siblings like secret-scan or dependency-cve-scan. It stops short of explicitly telling the agent to prefer this over those individual tools, so full sibling routing is implied rather than stated.

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?

It supplies concrete usage contexts ('CI pre-commit and supply-chain triage'), which is enough for an agent to recognize the intended scenario. It gives no exclusions or named alternatives for when a narrower scan would be better, so it lands at clear-context-without-exclusions rather than full routing 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