Skip to main content
Glama

audit_agent_skill_escrow

Idempotent

[Private] Is this agent skill safe to install? Scans SKILL.md and scripts for credential theft, remote code execution and hidden Unicode instructions. For a free preview with findings by file, call review_agent_skill_free with {}.

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": {
      "skillMarkdown": "<skillMarkdown>"
    },
    "name": "audit_agent_skill_escrow"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoSemantic version string (e.g. '1.0.0') for behavioral drift comparison.
skillMarkdownYesFull SKILL.md markdown content including YAML frontmatter.
targetAgentIdNoOptional agent or plugin ID to track version drift history.
bundledScriptsNoOptional helper script code bundled with the skill.
requiredSectionsNoRequired frontmatter or markdown headings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / bundledScripts / description
      Added value: +"Optional helper script code bundled with the skill."
    • addedInput schema / properties / requiredSections / description
      Added value: +"Required frontmatter or markdown headings."
    • addedInput schema / properties / skillMarkdown / description
      Added value: +"Full SKILL.md markdown content including YAML frontmatter."
    • addedInput schema / properties / targetAgentId
      Added value: +{
      +  "description": "Optional agent or plugin ID to track version drift history.",
      +  "type": "string"
      +}
    • addedInput schema / properties / version
      Added value: +{
      +  "description": "Semantic version string (e.g. '1.0.0') for behavioral drift comparison.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and closed-world, so the safety profile is largely covered. The description adds the scan scope and detection categories, which is real value, but never addresses the 'escrow' in the name - no mention of payment, cost, or what state is written to justify readOnlyHint=false - nor what the audit produces.

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?

Three tight sentences with the core question front-loaded and the alternative named last. The bracketed '[Private]' prefix is slightly opaque and the 'with {}' payload notation is terse, but nothing is padded.

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

Completeness3/5

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

With no output schema, the description should say what an audit returns (verdict, findings, severity) and it does not - it only describes the free sibling's per-file findings. Combined with the unexplained escrow/payment mechanics for a non-read-only tool, it leaves meaningful gaps for a 5-parameter audit call.

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?

Schema description coverage is 100%, so all five parameters are already documented, and the description only loosely maps 'SKILL.md and scripts' onto skillMarkdown and bundledScripts. It says nothing about version, targetAgentId drift tracking, or requiredSections, so baseline 3 is appropriate.

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?

States a concrete verb (scans) and resource (SKILL.md and scripts) plus the exact threat classes it looks for: credential theft, remote code execution, hidden Unicode instructions. It also explicitly positions itself against the sibling review_agent_skill_free, so an agent can distinguish the two without opening either schema.

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?

Gives an explicit routing rule: for a free preview with per-file findings, call review_agent_skill_free with an empty object, implying this tool is the private/full audit. It stops short of stating the condition that should make an agent pick this one (cost, depth, escrow requirement), so the choice is implied rather than spelled out.

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.