Skip to main content
Glama

Vibes-Coded Agent Security and Commerce Tools

by io.github.doteyeso-ops

health

Read-onlyIdempotent

Return MCP server liveness: version, origin, tool count, and catalog size.

Use for hosted inspector probes (Glama / Smithery) or before diagnosing tool failures.
Do not use for business outcomes — call vc_* tools or pay(slug=...) instead.

No auth required. No side effects.
Returns JSON {ok, service, version, origin, tools, catalog_resources}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.7/5.0
Behavior4/5

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

The description adds behavioral context beyond the annotations by stating 'No auth required. No side effects.' and by describing the JSON response shape. This complements the existing readOnlyHint/idempotentHint/destructiveHint annotations, though rate-limit or failure-mode behavior is not discussed.

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?

The description is compact and every sentence earns its place: purpose, usage, exclusions, safety, and return shape are each covered without redundancy. Key information is front-loaded in the first sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter health check with annotations and an output schema already present, the description is complete. It covers what the tool returns, when to use it, when not to use it, alternatives, authentication, and side-effect profile.

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?

The tool has zero parameters, so there is nothing for the description to explain about inputs. The baseline of 4 applies because no parameter documentation is needed beyond the empty input schema.

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 opens with a specific verb and resource: 'Return MCP server liveness' and names the exact fields returned (version, origin, tool count, catalog size). It clearly distinguishes health from the vc_*/pay siblings by explicitly saying it is not for business outcomes.

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

Usage Guidelines5/5

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

It states exactly when to use the tool: hosted inspector probes such as Glama/Smithery, or before diagnosing tool failures. It also provides a clear exclusion and alternatives: do not use for business outcomes; call vc_* tools or pay(slug=...) instead.

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