Skip to main content
Glama
Sign In
Txa_MCP

Txa_MCP

by TXAVLOG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_repositories

Retrieve Git information for the current directory, including remote, branch, and status. This clarifies version control state for local workspace diagnostics.

Instructions

Get Git information for the current directory (Remote, Branch, Status).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.3

TDQS

B3.4/5.0
Behavior3/5

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

Without annotations, the description carries the full transparency burden. It discloses the specific data items returned (Remote, Branch, Status) and the operational scope (current directory), but it does not mention error scenarios (e.g., not a git repository), read-only nature, or any side effects. This is acceptable for a simple read-only tool but leaves gaps.

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?

The description is a single, front-loaded sentence with no redundant words. It states exactly what the tool does and what it returns, achieving maximum efficiency.

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?

Given the tool's simplicity (no params, no output schema), the description is mostly complete. However, the name conflict with 'list_repositories' and the overlap with sibling 'git_status' create ambiguity. A note on when to use this over git_status would improve completeness.

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?

The tool has zero parameters, so the baseline is 4. The description adds the implicit context of 'current directory', which clarifies the scope of the operation. No further parameter explanation is needed.

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 clearly states the verb 'Get' and the resource 'Git information for the current directory' with specific fields (Remote, Branch, Status). However, it does not distinguish from the sibling tool 'git_status', which likely provides similar information, and the tool name 'list_repositories' is somewhat misleading.

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 provides no guidance on when to use this tool versus alternatives like 'git_status' or 'git_log'. It does not mention exclusions, prerequisites, or the specific context in which this tool is preferred.

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