Skip to main content
Glama
Sign In
reposynapse

reposynapse

by Jul879n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_complexity

Identify functions exceeding line or parameter thresholds, producing compact output to prioritize refactoring without scanning every file.

Instructions

List functions/methods above complexity thresholds (too many lines or params). Ultra-compact output to help prioritize what to refactor without reading every file.

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

Input Schema

NameRequiredDescriptionDefault
min_linesNoMinimum lines in function body to flag (default: 30)
min_paramsNoMinimum parameter count to flag (default: 4)
file_patternNoGlob pattern to limit analysis (e.g. "src/**/*.ts"). Omit to scan all source files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It reveals 'ultra-compact output' as a return trait and implies a read-only scan, but it does not explain whether thresholds combine, how results are ordered, or what specific fields are 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?

Two sentences with no filler. The core function is stated first, followed by the purpose and output trait. Every sentence earns its place.

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?

For a tool with three optional, fully documented parameters and no output schema, the description provides enough context to invoke correctly: what it lists, why to use it, and what the output is like. It could detail the output format, but that is not essential for a simple analysis tool.

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%, and each parameter already has a clear description with defaults and an example for file_pattern. The description adds no significant meaning beyond the schema, 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?

The description uses a specific verb ('List') and resource ('functions/methods') with a clear criterion ('above complexity thresholds... too many lines or params'). This clearly distinguishes it from sibling tools like read_file or search_in_file.

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?

The phrase 'to help prioritize what to refactor without reading every file' provides a clear use case and context. It doesn't explicitly name alternatives or exclusion conditions, but the intended scenario is evident.

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