Skip to main content
Glama
Sign In
claude-engram

claude-engram

by 20alexl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_similar_issues

Find code issues matching a regex pattern across your codebase. Locate similar bugs like empty except blocks, with options to filter by file type and exclude paths.

Instructions

Search codebase for bug pattern (e.g., 'except:\s*pass').

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": {
      "issue_pattern": "<issue_pattern>",
      "project_path": "<project_path>"
    },
    "name": "find_similar_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_patternYesRegex pattern
project_pathYes
file_extensionsNo
exclude_pathsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does not disclose behavioral traits such as read-only nature, potential performance impact, or whether results are limited to matches or include context.

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?

The description is a single concise sentence with a useful example. However, it could include more context without becoming verbose.

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?

Given 4 parameters with only 25% schema coverage and no output schema, the description should compensate. It falls short by not explaining return values, parameter usage, or behavioral expectations.

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?

Only issue_pattern has a schema description ('Regex pattern'), and the tool description only provides an example pattern. No explanation for project_path, file_extensions, or exclude_paths, leaving their roles ambiguous.

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 explicitly states the action ('Search codebase') and the resource ('bug pattern'), with a concrete example ('except:\s*pass'). This clearly distinguishes from siblings like code_pattern_check, which likely handles general patterns.

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_pattern_check or others. The description lacks context on prerequisites or scenarios where this tool is preferred.

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