Skip to main content
Glama
Sign In
reflens

reflens

by cybertronayush
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

reflens_history

Retrieve recent git commits and file change history to understand how and why code evolved.

Instructions

Historical context from the reference repo's live git history: recent commits for the whole repo, or the change history of a specific file (hash, date, author, subject). Use to understand how/why code evolved. Only available when the repo was ingested from a live git directory.

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": {
      "repo": "<repo>"
    },
    "name": "reflens_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYes
limitNo
targetNoOptional file path; omit for repo-wide.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses that the tool requires a live git directory and returns commit details (hash, date, author, subject). It implies a read-only operation, which is sufficient for this simple tool.

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, no wasted words, front-loaded with key information. 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?

Given no output schema, the description lists the return fields (hash, date, author, subject), which is helpful. It also covers a prerequisite. For a history query tool, this is fairly complete, though additional detail on order or pagination could improve it.

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 description coverage is only 33% (only target has a description). The description adds meaning by explaining that repo and target determine scope (whole repo vs specific file), and the limit is implied but not detailed. This compensates for the low coverage.

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 clearly states the tool provides historical context from git history, listing fields like hash, date, author, and subject. It distinguishes itself from siblings (reflens_list, reflens_search, etc.) by focusing on history.

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 description explicitly states the use case 'to understand how/why code evolved' and the prerequisite 'only available when the repo was ingested from a live git directory.' It does not provide explicit alternatives or when-not-to-use, but the context is clear.

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