Skip to main content
Glama

krusch_git_read_blob

Read-onlyIdempotent

Extract bounded lines from a file in a Git repository using start and end line numbers. Enables targeted inspection of code or data without reading the full file.

Instructions

Read bounded lines from a file in the repository.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
repoNo
end_lineNo
start_lineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already supply the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the description only needs to add operational context. 'Bounded lines' usefully signals that reads are line-ranged rather than whole-file, but it omits what the bound is, whether there is a maximum line count, and how truncation or out-of-range requests behave.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though the extreme brevity leaves too much unsaid for a tool with four undocumented parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four parameters at 0% schema coverage and no output schema, the description is the only source of semantics, and it covers neither the repo selector nor the line-range behavior. For a file-read tool whose main risk is silent truncation or reading the wrong repository, this leaves material gaps.

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?

Schema description coverage is 0%, so the description must carry the meaning of all four parameters. It only loosely implies 'path' and the start/end line pair via 'bounded lines', and says nothing at all about the 'repo' parameter or about whether line numbers are 0- or 1-based, inclusive, or defaulted.

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 names a specific verb and resource: 'Read bounded lines from a file in the repository.' That is enough to distinguish a line-range file read from a tree listing or symbol lookup, but it never explicitly contrasts itself with the nearby file-reading siblings such as krusch_git_read_tree or krusch_fs_read_page.

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 when-to-use or when-not-to-use guidance, and no named alternative. An agent gets no help deciding between this, krusch_git_read_tree, and krusch_fs_read_page when it needs file content, nor any hint about prerequisites such as a valid repo selection.

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