Skip to main content
Glama
devatraj

AI-Code-Reviewer

by devatraj

get_index_status

Check if a repository's code index is up-to-date with its HEAD commit and view index size statistics to ensure accurate code review.

Instructions

Report whether a repo has been indexed, whether the index is stale relative to its current HEAD commit, and basic index size stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repo_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
staleYes
indexedYes
indexed_atYes
total_filesYes
total_chunksYes
embedding_modelYes
current_head_shaYes
last_indexed_commit_shaYes
Behavior4/5

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

No annotations provided, but the description clearly indicates a read-only reporting operation. It explicitly describes what is checked (indexed status, staleness, size stats). Could mention it is non-destructive, but the word 'Report' implies that.

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?

Single sentence front-loads purpose and includes relevant details. No wasted words, though could be more succinct.

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

Completeness5/5

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

Given the tool has one parameter and an output schema, the description is complete. It covers all key aspects of what the tool reports without needing to detail return values.

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?

Schema description coverage is 0% and the description does not elaborate on the repo_path parameter. The parameter's purpose is obvious but the description fails to add meaning beyond the schema.

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 reports index status, staleness relative to HEAD, and size stats. It distinguishes from siblings like index_repo (which modifies) and review tools (which review diffs/files).

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

Usage Guidelines3/5

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

No explicit guidance on when to use or when not to use. Usage is implied by name and description, but no alternatives or exclusions are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/devatraj/AI-Code-Reviewer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server