Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Analyze Methods

cc_analyze_methods
Read-onlyIdempotent

Analyzes methods in Python, JavaScript, or TypeScript files, with optional class filtering, to return parameters, visibility, and Python complexity, data-flow, and guardrail details.

Instructions

Detailed method analysis of a Python, JavaScript, or TypeScript file.

Args:

  • path (string): Path to a .py, .js/.jsx/.mjs/.cjs, or .ts/.tsx/.mts/.cts file

  • class_name (string, optional): Only methods of this class

Returns:

  • Methods with parameters and visibility; Python analysis also includes decorators, complexity, data flow, and BACH guardrails

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": {
      "path": "<path>"
    },
    "name": "cc_analyze_methods"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to a supported Python, JavaScript, or TypeScript file
class_nameNoOnly analyze this class

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.27
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / path / description
      Previous value: -"Path to the Python file"New value: +"Path to a supported Python, JavaScript, or TypeScript file"
  2. First observedv1.3.8

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safe read-only nature, but the description adds real value beyond them: it discloses the supported file extensions and, importantly, that output differs by language (Python adds decorators, complexity, data flow, BACH guardrails). It does not mention behavior on unsupported files or analysis limits on very large files.

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?

Front-loaded one-line purpose followed by tight Args/Returns blocks; every line carries information. The Args block partly mirrors the schema, but the extension list and class_name semantics are not pure repetition.

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?

With no output schema, the Returns block is essential and present, including language-dependent output differences. Minor gaps remain: no mention of result size limits, pagination, or error behavior for invalid paths.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description earns extra credit by enumerating the exact accepted extensions (.py, .js/.jsx/.mjs/.cjs, .ts/.tsx/.mts/.cts) where the schema only says 'supported ... file', and by restating class_name as a narrowing filter on methods.

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 (analyze) and resource (methods) scoped to Python/JavaScript/TypeScript files, and the return line clarifies it yields methods with parameters and visibility. This makes it distinguishable from cc_analyze_code and cc_extract_classes by inference, though neither sibling is named.

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

Usage Guidelines3/5

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

Usage is implied by the narrow scope ('method analysis', optional class_name filter), but there is no explicit guidance on when to prefer this over cc_analyze_code or cc_extract_classes, and no stated exclusions or prerequisites.

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