Skip to main content
Glama

review_agent_skill_free

Read-onlyIdempotent

Free static review of an agent skill and related text files, with findings by file, line and rule. Call with {} for a fictional JSON example, or send files to review.

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

Input Schema

NameRequiredDescriptionDefault
filesNoText files with a root SKILL.md. Maximum 32768 UTF-8 bytes per file and 98304 in total. Omit files to see the free sample JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: the review is static (no execution), and results are organized by file, line and rule. It stops short of describing rule coverage or what happens when limits are exceeded, which the schema handles instead.

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?

A single sentence that front-loads what the tool does and then gives the two invocation modes; no filler, no restatement of the title.

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?

No output schema exists, and the description compensates by sketching the return shape (findings keyed by file, line, rule). Combined with 100%-covered input schema and full annotations, an agent has enough to call it correctly; only rule-catalog and failure behavior are unstated.

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?

Only one optional parameter and schema description coverage is 100%, including the 8-file/32KB-per-file/96KB-total limits and the 'omit to see the free sample' behavior. The description restates that same omit-to-sample behavior but adds no format or ordering guidance beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('static review of an agent skill and related text files') plus the shape of the output ('findings by file, line and rule'). It does not name or contrast itself with any sibling, though none of the listed siblings is a skill-review tool, so the risk of confusion is low.

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?

Explicitly gives the two invocation modes: call with {} to get a fictional sample JSON, or send files for an actual review. Clear context for both paths, but no exclusions or prerequisites (e.g., what makes a skill reviewable) and no statement about the paid counterpart.

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.