Skip to main content
Glama
altcheck

altcheck

vet_repo

Vet a GitHub repository before adoption to get a VIABLE, RISKY, or AVOID verdict with clear reasons.

Instructions

Vet a single GitHub repo (owner/name) before adopting it: VIABLE / RISKY / AVOID with reasons.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repo": "<repo>"
    },
    "name": "vet_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesowner/name, e.g. "makeplane/plane"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the output taxonomy (VIABLE / RISKY / AVOID with reasons), which tells the agent this is an analytical read rather than a mutation. It says nothing about cost, network/auth requirements, or what evidence feeds the verdict, leaving meaningful behavioral gaps for a no-annotation tool.

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?

One tight sentence with the scope and the expected output front-loaded; nothing is wasted. It is short to the point of omitting context that would have helped, but there is no filler.

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

Completeness4/5

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

For a one-parameter read-only analysis tool with no output schema, the description covers input scope and the shape of the result. What is missing — verdict criteria, failure modes, cost — is secondary but not trivial given the absence of annotations.

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

Parameters3/5

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

The single parameter is already 100% documented in the schema, including the owner/name format and an example. The description merely restates "(owner/name)" and adds no constraint or meaning beyond the schema, so baseline 3 applies.

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?

Names a specific verb and resource ("Vet a single GitHub repo") and states the decision output (VIABLE / RISKY / AVOID with reasons), so an agent knows exactly what it gets back. It does not explicitly contrast itself with the sibling find_alternatives, 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 Guidelines3/5

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

"before adopting it" gives a clear situational trigger for calling the tool, which is more than nothing. However there are no exclusions (e.g. when not to vet, private repos, orgs) and the sibling find_alternatives is never referenced, so routing must be inferred from its name alone.

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