Skip to main content
Glama
Sign In
claude-engram

claude-engram

by 20alexl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

audit_batch

Audit multiple files for issues using glob patterns. Specify file paths and optionally filter by minimum severity: critical, warning, or info.

Instructions

Audit multiple files for issues. Supports glob patterns.

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": {
      "file_paths": "<file_paths>"
    },
    "name": "audit_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathsYes
min_severityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

Only mentions glob pattern support. No disclosure of read-only nature, permissions, or other behavioral traits. With no annotations, description should carry this burden but fails to.

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?

Two sentences, efficient and front-loaded. No unnecessary words, though slightly under-detailed.

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

Completeness2/5

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

Missing return value description, behavior for empty paths, error cases, and meaning of min_severity. Given no output schema and no annotations, description is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Glob pattern support adds value for file_paths but min_severity is completely unexplained. With 0% schema coverage, description should compensate more.

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?

Clearly states it audits multiple files for issues, with glob support. Distinguishes from sibling audit tools like code_quality_check by focusing on file batches.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like code_quality_check or scout_search. Missing context about prerequisites or selection criteria.

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

Deploy Server

Other Tools