Goodeye

check_skill_safety

Run both system safety verifiers against a saved skill version.

Resolves a UUID or owner-scoped slug. Visibility mirrors get_skill: owner or any active grant; cross-user pointers surface as not found. Defaults to the latest version. Bills two metered verifier runs against the caller. The combined status is one of clean, flagged, blocked, or error; per-side block and advisory carry the verifier id, version, run id, verdict, and reasoning.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`version`	No	Pin to a specific version number; omit to use the latest version.
`skill_id`	Yes	The skill to act on, identified by its UUID, slug, or name.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 18, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds value beyond annotations by disclosing billing ('Bills two metered verifier runs') and enumerating possible statuses ('clean', 'flagged', 'blocked', or 'error') with per-side details. No contradiction with annotations.

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 concise (~80 words) and well-structured: first sentence states purpose, then details resolution, visibility, billing, and output. No extraneous content.

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 safety check tool, the description covers input resolution, visibility rules, billing impact, and output format (status with per-verifier details). Completeness is adequate given output schema exists.

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?

With 100% schema coverage, description adds context: explains 'skill_id' resolution (UUID/slug) and that 'version' defaults to latest. This provides meaning beyond the 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 starts with a specific verb+resource+scope: 'Run both system safety verifiers against a saved skill version.' It clearly distinguishes from siblings like 'run_verifier' by specifying it runs two system verifiers, not a single one.

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 provides context on resolution (UUID/slug) and visibility (owner or grant), and mentions defaulting to latest version. However, it does not explicitly state when NOT to use this tool or compare to alternatives like 'run_verifier'.

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

All Goodeye tools Inspect

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.