Skip to main content
Glama
vighriday

Veris

by vighriday
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

register_repo

Registers a local repository in the user-level registry so cross_repo_snapshot can include it, verifying the path is an existing directory with .git.

Instructions

Adds a repository to the user-level registry at ~/.veris/registry.json so cross_repo_snapshot includes it. The path must exist, be a directory, and contain a .git directory. Setup-time call, typically run once per repository.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable name shown in snapshots.
pathYesAbsolute path to the repository root.
tagsNoOptional grouping tags, e.g. ['prod','checkout'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.1
    • changedInput schema / properties / name / description
      Previous value: -"Human-readable repo name. Shown in cross-repo snapshots."New value: +"Human-readable name shown in snapshots."
    • changedInput schema / properties / path / description
      Previous value: -"Absolute filesystem path to the repository root."New value: +"Absolute path to the repository root."
    • changedInput schema / properties / tags / description
      Previous value: -"Optional tags for grouping (e.g. ['frontend','prod','checkout-flow'])."New value: +"Optional grouping tags, e.g. ['prod','checkout']."
  2. Changed3 schema fields changedv2.1.10
    • addedInput schema / properties / name / description
      Added value: +"Human-readable repo name. Shown in cross-repo snapshots."
    • addedInput schema / properties / path / description
      Added value: +"Absolute filesystem path to the repository root."
    • addedInput schema / properties / tags / description
      Added value: +"Optional tags for grouping (e.g. ['frontend','prod','checkout-flow'])."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description fully discloses side effects (writes to ~/.veris/registry.json) and prerequisites (path must exist, be a directory, contain .git). This goes beyond the schema and gives the agent essential behavioral context. It doesn't mention error handling or overwrite semantics, but for a one-time setup call this is acceptable.

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?

Two sentences: first states purpose and effect, second lists constraints and timing. All information is front-loaded, no filler, and every clause earns its place.

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 simple registration tool, the description covers what, where, prerequisites, and when to use. No output schema is needed, and an agent has all information required to call it correctly without additional inference.

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% with descriptive parameter comments. The description adds meaningful constraints on the path parameter (must exist, be a directory, contain .git), which is critical for correct invocation. This goes beyond the schema's basic 'Absolute path to the repository root'.

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?

States a specific verb ('Adds'), a resource (repository to user-level registry), the target file path, and the downstream effect (included in cross_repo_snapshot). Clearly distinguishes from sibling tools like cross_repo_snapshot, which consumes the registry, and analysis tools.

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

Usage Guidelines4/5

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

Explicitly calls out 'Setup-time call, typically run once per repository,' giving clear timing and frequency guidance. While it doesn't list alternative tools for comparison, the setup vs. usage distinction is sufficient and directly implied by the 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