Skip to main content
Glama
Sign In
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sqo_git_forensics

Mines git log commit co-occurrence to reveal un-imported files that always change together and historical bug-magnet files, exposing hidden coupling before you edit code.

Instructions

Git Evolutionary Forensics — Invisible Co-Change Twins & Bug-Magnet Miner (v12.0 Quantum): mines git log commit co-occurrence matrices to reveal un-imported files that always change together (>=55% coupled) + historical bug-magnet files.

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": {
      "workspace": "<workspace>"
    },
    "name": "sqo_git_forensics"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace root directory.
max_commitsNoMax commits to mine (default: 120).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv13.0.0

TDQS

B3.1/5.0
Behavior3/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 usefully discloses the co-occurrence mining approach and the >=55% coupling threshold, but it does not state that the operation is read-only, describe performance characteristics, or explain the result format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded after the colon, and the coupling threshold is useful. However, branding such as 'Invisible Co-Change Twins' and '(v12.0 Quantum)' adds noise without helping an agent invoke the tool correctly.

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 two-parameter analysis tool with no output schema, the description explains the mining concept and threshold but omits the return structure and practical usage context. It is adequate but leaves important invocation and interpretation details implicit.

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%, so both `workspace` and `max_commits` are already documented in the schema. The description adds no additional parameter semantics beyond the schema baseline.

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?

The description states a specific resource and analysis target: mining `git log` commit co-occurrence matrices to reveal highly coupled un-imported files and historical bug-magnet files. It is clear what the tool produces, though it does not explicitly distinguish itself from related siblings such as code-hotspot or dead-code tools.

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?

The description does not say when to use this tool, when not to use it, or which sibling tool is the better alternative. Usage is only implied by the forensic co-change and bug-magnet concepts.

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