Skip to main content
Glama

repo_hotspots

Read-onlyIdempotent

Lists files by recorded Git change frequency to reveal code hotspots and guide review or refactoring.

Instructions

List files with the most recorded Git changes.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is fully covered. The description adds the meaningful concept of ranking files by change frequency, but says nothing about how the ranking is computed (commit count vs. lines changed), the time window, or default ordering, which are the behaviors an agent would actually need.

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 filler; everything stated is relevant and nothing is padded. Brevity is not the problem here — omission is.

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 read-only listing tool with full annotation coverage, a one-line description is close to sufficient, but the undocumented 'limit' parameter and the unstated ranking metric leave the agent guessing on both invocation and interpretation of results. There is no output schema, so the description is the only place the ranking semantics could have been explained.

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?

There is one parameter, 'limit', with 0% schema description coverage and no mention in the description. It is left ambiguous whether limit is a maximum file count, a depth, or a time bound, and no default is stated — the description should compensate for the empty schema and does not.

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 pairs a concrete verb ('List') with a well-defined resource ('files with the most recorded Git changes'), which effectively explains the 'hotspots' concept. It does not, however, distinguish itself from plausible siblings such as repo_changes or repo_history, so an agent cannot tell from this text alone which one returns ranked churn.

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?

There is no guidance on when to use this versus other repo tools, no prerequisites, and no note about what 'recorded' means (local repo only, given openWorldHint=false). The agent must infer the use case entirely from the title.

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