Skip to main content
Glama

RepoPilot

by app.repopilot
OverviewDiscussionsAdmin

Orient an agent in an unfamiliar repository

get_artifact
Read-onlyIdempotent

CALL before substantial code work in an unfamiliar repository when the agent needs key files, entry points, architecture hypotheses, a reading order, and verify-before-trusting guidance. Returns the cached CLAUDE.md-style artifact or Cursor rules. Do not call again if the artifact is already in context. Takes NO artifact id: name the repository itself. Minimal call: {"repo":"vercel/next.js"}. Pass exactly one of repo or package, each a plain string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoNoPublic GitHub repository as owner/repo or a github.com URL.
ownerNoRepository owner, when repo carries only the bare name. Optional: prefer the single owner/repo form in repo.
formatNoOptional. markdown for CLAUDE.md-style guidance (the default); cursor for .mdc rules.markdown
packageNonpm package name, for example lodash or npm:@scope/pkg. To judge a specific VERSION rather than the package as a whole, use evaluate_dependency_change instead.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYes
agentYes
statusYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / description
      Added value: +"Name one repository (or one npm package) as a plain string. There is no artifact id in this contract. Minimal valid call: {\"repo\":\"vercel/next.js\"}."
    • addedInput schema / examples
      Added value: +[
+  {
+    "repo": "vercel/next.js"
+  },
+  {
+    "format": "cursor",
+    "repo": "vercel/next.js"
+  },
+  {
+    "package": "lodash"
+  }
+]
    • changedInput schema / properties / format / description
      Previous value: -"markdown for CLAUDE.md-style guidance; cursor for .mdc rules."New value: +"Optional. markdown for CLAUDE.md-style guidance (the default); cursor for .mdc rules."
    • addedInput schema / properties / owner
      Added value: +{
+  "description": "Repository owner, when repo carries only the bare name. Optional: prefer the single owner/repo form in repo.",
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / package / description
      Previous value: -"npm package name, for example lodash or npm:@scope/pkg."New value: +"npm package name, for example lodash or npm:@scope/pkg. To judge a specific VERSION rather than the package as a whole, use evaluate_dependency_change instead."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already assert read-only, idempotent, open-world, and non-destructive behavior; the description adds cache semantics ('cached CLAUDE.md-style artifact'), verify-before-trusting guidance, and a caution about context reuse. No contradiction with annotations. It doesn't address staleness or auth, but the annotation profile lowers the burden.

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 front-loads the when-to-call condition, then gives output, cancellation, and input-constraint guidance in compact sentences. Every sentence earns its place, and the minimal-call example is a high-value addition rather than filler.

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?

For a low-complexity, 4-parameter, read-only tool with a rich schema, an output schema, and safety annotations, the description covers when, why, how to call, and when not to call. Nothing essential is missing for an agent to invoke it correctly.

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?

Schema coverage is 100%, so the baseline is 3; the description adds value beyond the schema by stating that there is no artifact id, that exactly one of repo or package must be supplied, and that each must be a plain string. The minimal-call example reinforces the required shape without repeating every schema property.

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 concrete resource (repository/package), a precise action (return the cached CLAUDE.md-style artifact or Cursor rules), and a clear purpose (orient the agent before substantial code work). It also clarifies that there is no artifact id, avoiding confusion with the tool name. It does not explicitly differentiate from siblings like analyze_repo or compare_repos, so it stops 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 Guidelines5/5

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

It gives an explicit trigger condition ('CALL before substantial code work in an unfamiliar repository when...'), a clear do-not-call rule ('Do not call again if the artifact is already in context'), and an explicit alternative for version-specific judgment (evaluate_dependency_change in the package parameter). This fully routes the agent.

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

All RepoPilot toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources