Skip to main content
Glama

pare_check

Scans Python and JS/TS files to detect AI test landmines and hollow error handling, helping you find risky test shortcuts before they hide real failures.

Instructions

Scan Python and JS/TS files for AI test landmines and hollow error handling.

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

Input Schema

NameRequiredDescriptionDefault
pathsNoFiles or directories to check (defaults to current directory).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only scan but does not explicitly state side effects, permissions, whether files are modified, or what kind of result is returned.

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 front-loaded sentence with no wasted wording. It is concise and easy to parse, even though the phrase "AI test landmines" is not self-explanatory.

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?

For a simple one-parameter scanner, the description covers the basic invocation context and schema covers the path argument. However, with no annotations and no output schema, it leaves meaningful gaps around output format and behavioral side effects.

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% for the single paths parameter, so the schema already documents its meaning and default. The description adds no additional parameter semantics, making the baseline 3 appropriate.

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: "Scan Python and JS/TS files" for particular problem classes. The target phrase "AI test landmines" is somewhat jargon-like, and the description does not distinguish this tool from siblings such as pare_debt or pare_recall.

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?

Gives no explicit when-to-use guidance, exclusions, or alternatives. It only describes what the scan does, leaving the agent to infer when pare_check is preferable to the sibling tools.

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