Skip to main content
Glama
Sign In

Profullstack

by com.profullstack
OverviewDiscussionsAdmin

vu1nz: Scan Repo CI/CD Security

vu1nz_scan_repo
Read-onlyIdempotent

[vu1nz] Run vu1nz's 6 deterministic CI/CD security checks against any public GitHub repository's workflow files. Returns findings with severity, file, line, CWE, and recommendation.

Served by vu1nz (https://vu1nz.com/mcp).

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

Input Schema

NameRequiredDescriptionDefault
repoYesGitHub repo in 'owner/repo' format (or a full github.com URL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real value beyond them: exactly six deterministic checks, a network scan of a remote repo, and a concrete finding shape including CWE mapping. It omits rate limits, auth requirements, and whether private repos are simply rejected.

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?

Two short sentences that front-load the action, scope, and return shape with no filler; the trailing 'Served by vu1nz' attribution is boilerplate but harmless. Nothing an agent needs is buried.

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, read-only scan tool with full annotation coverage, the description supplies purpose, target scope, and output fields, which is close to sufficient. The only meaningful gap is how large repos or failures (private/missing repo, invalid slug) are surfaced.

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?

With a single parameter at 100% schema coverage, the schema already documents the 'owner/repo' or full-URL format. The description contributes only the implicit 'public' restriction and 'workflow files' scoping, so it matches the baseline of 3 rather than adding syntax or format detail.

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?

The description names a specific operation ('Run vu1nz's 6 deterministic CI/CD security checks') and a precisely bounded target ('any public GitHub repository's workflow files'), which no sibling tool shares. It also states what comes back (severity, file, line, CWE, recommendation), so an agent can tell this is the scanning action rather than the advisory/blog/check-listing siblings.

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?

Usage scope is implied by 'any public GitHub repository's workflow files', which usefully rules out private repos, but there is no explicit when-to-use or when-not-to-use statement and no named alternative (e.g. vu1nz_list_checks for just enumerating check definitions). The agent must infer the routing decision from the enumerable sibling set.

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

All Profullstack toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources