Skip to main content
Glama
cloud-Xolt

local-repo-mcp

by cloud-Xolt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

repo_read_file

Securely reads a file from a local Git repository using its path, enabling agents to access code context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
bytesYes
contentYes
repositoryYes
content_trustYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.4.0
    • addedOutput schema / $defs
      Added value: +{
+  "RepositoryRef": {
+    "properties": {
+      "name": {
+        "title": "Name",
+        "type": "string"
+      },
+      "root": {
+        "title": "Root",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "root"
+    ],
+    "title": "RepositoryRef",
+    "type": "object"
+  }
+}
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties
      Added value: +{
+  "bytes": {
+    "title": "Bytes",
+    "type": "integer"
+  },
+  "content": {
+    "title": "Content",
+    "type": "string"
+  },
+  "content_trust": {
+    "const": "untrusted_repository_data",
+    "title": "Content Trust",
+    "type": "string"
+  },
+  "path": {
+    "title": "Path",
+    "type": "string"
+  },
+  "repository": {
+    "$ref": "#/$defs/RepositoryRef"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "path",
+  "bytes",
+  "content",
+  "content_trust",
+  "repository"
+]
    • changedOutput schema / title
      Previous value: -"repo_read_fileDictOutput"New value: +"ReadFileResult"
  2. First observedv0.1.0

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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