Skip to main content
Glama

krusch_git_read_tree

Read-onlyIdempotent

Lists files and directories at a given path inside a repository, letting agents inspect repo structure before reading or editing files.

Instructions

List files and directories at a given path inside the repository.

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

Input Schema

NameRequiredDescriptionDefault
pathNo
repoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

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, non-destructive and closed-world, so the safety profile is covered. The description adds only the fact that both files and directories are returned; it says nothing about recursion depth, ordering, or path resolution relative to the repo root.

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 tight sentence with the resource and scope front-loaded and no filler. Nothing is wasted or buried.

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 read tool with rich annotations this is close, but the description omits what happens with an empty path (the default), whether the listing is recursive or single-level, and what 'repo' selects. Those omissions matter because no output schema exists to clarify the returned shape.

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% for both parameters, so the description must carry the semantics. It clarifies only that 'path' scopes the listing inside the repository; 'repo' is never mentioned, nor is the meaning of the empty-string default for path.

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?

Specific verb plus resource plus scope: 'List files and directories at a given path inside the repository' tells an agent exactly what it returns and where. It does not distinguish itself from near-neighbors such as krusch_fs_page_tree or krusch_git_file_symbols, so it falls short of a 5.

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 gives no when-to-use or when-not-to-use guidance and names no alternative. An agent must infer from tool names alone whether to use this or krusch_fs_page_tree for directory exploration.

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