Skip to main content
Glama

Vibes-Coded Agent Security and Commerce Tools

by io.github.doteyeso-ops

vc_skill_risk_scan

Read-onlyIdempotent

Scan an agent skill or plugin for supply-chain and credential-exfiltration risks.

Use before installing untrusted SKILL.md files, MCP plugins, npm packages, or setup scripts.
Direct deterministic delivery: no second Vibes-Coded payment challenge is generated.
Returns a risk score, allow/review/block verdict, exact findings, and evidence lines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesComplete SKILL.md, plugin manifest, installer, or source text to scan (max 200,000 characters).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior, and the description adds the operational guarantee that no second Vibes-Coded payment challenge is generated. This is useful context beyond the annotations, though the phrase is somewhat jargon-heavy and does not describe potential network or external-service behavior.

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?

The description is concise and well-structured: action, usage context, operational guarantee, and result summary. The 'Vibes-Coded' phrasing is catchy but slightly unclear, and listing return values is somewhat redundant given the output schema.

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?

The description covers purpose, when to use it, what input to provide, what to expect behaviorally, and what results are returned. The output schema and annotations cover the remaining details. The main gap is not explaining how this tool relates to vc_skill_scan_consensus for an agent deciding between them.

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?

The input schema covers the single parameter completely, including accepted content types and the 200,000-character limit. The description adds little parameter-level detail beyond what the schema already provides, so it appropriately stays at the baseline.

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 clearly states the tool scans agent skills or plugins for supply-chain and credential-exfiltration risks, which is a specific verb and resource. It does not explicitly contrast itself with the sibling vc_skill_scan_consensus tool, so it stops short of full sibling differentiation.

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?

The description gives concrete usage guidance: use before installing untrusted SKILL.md files, MCP plugins, npm packages, or setup scripts. It does not state when not to use the tool or mention any alternative tools, so it lacks explicit exclusions or sibling routing.

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

All Vibes-Coded Agent Security and Commerce Tools toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools target a clearly distinct resource and action: notepad save/read/list/share/browse is cleanly separated from workspace create/read/write/list, and pairs like vc_web_search vs vc_page_markdown have explicit boundaries. The four guard tools (state, drift, idempotency, retry storm) share the same advisory-preflight pattern and could be confused at a glance, though their differing nouns and sibling cross-references reduce misselection.

Naming Consistency4/5

The vc_<domain>_<action> convention with the action verb last is consistent across most tools (v_c_notepad_save, v_c_workspace_create, v_c_square_post, v_c_drift_guard, v_c_attest_verify). Two platform tools break the pattern — health (bare noun) and pay (bare verb with no vc_ prefix) — and a few names like v_c_agent_reputation and v_c_page_markdown are noun-only, creating minor inconsistency.

Tool Count3/5

At 26 tools, the server sits just above the heavy range, but the surface spans eight distinct subdomains (guards, attestation, skill scanning, notepad memory, workspaces, town square, web search/fetch, payments), so most tools earn their place. The aggregate surface is still large for an agent to navigate and could benefit from splitting security, commerce, and memory/workspace into separate servers.

Completeness3/5

Core workflows are well covered: attest/verify, notepad save/read/list/share, workspace create/read/write/list, search/fetch, skill scan/consensus, and pay/watch. Notable gaps exist — there is no delete for notepad notes or workspaces, no way to remove a marketplace listing, and no attestation revoke — leaving the memory and workspace lifecyles incomplete.

Resources