Skip to main content
Glama

setup

Set verifAIed up for a repository. Free. Call this first after the verifAIed MCP is connected, and again after each step.

Pass the repository as owner/repo from the git remote (a repo UUID also works) and the current git branch; the default branch is used when branch is omitted.

Returns an ordered checklist. Each step has a status:

  • done: the server saw the result (a committed file, an analysis for the branch). No action.

  • todo: required and not done. commands and files say exactly what to run and write.

  • check_locally: required, but only your machine can tell (the CLI on PATH, the CLI's login). Run verify; carry the step out if it fails.

  • recommended: not required; verifAIed asks you to offer it to the user rather than skip it.

  • optional: not required; mention it once.

next_step names the step to do now and complete is true when no required step is left. A step with needs_user true needs a person — for cli_token, to approve the verifaied login you run in the browser. This tool never mints or returns a token.

This tool reads the repository through the GitHub App and never changes it. You write the files; the user commits them. facts says what was read, and facts.github_reachable is false when the tree could not be read, in which case every step the tree would have settled is check_locally.

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": {
      "repository": "<repository>"
    },
    "name": "setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNo
repositoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses read-only repository access via the GitHub App ('never changes it'), the split of responsibility ('You write the files; the user commits them'), and that it never mints or returns a token. It also flags the auth/browser dependency for `cli_token` and the degradation path when `facts.github_reachable` is false.

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?

The description is front-loaded with the purpose and call timing, then structured into a scannable status list. It is dense but nearly every line encodes a distinct rule; the fixed-width name formatting and line wrapping add mild visual noise without bloat.

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?

There is no output schema, so the description must explain the return value, and it fully documents the checklist shape: the five `status` values and their required actions, `next_step`, `complete`, `needs_user`, and `facts`. For a two-parameter orchestrator tool, nothing an agent needs to act on the response is missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate, and it does: `repository` is specified as ``owner/repo`` taken from the git remote with a UUID alternative, and `branch` is described as the current git branch with the default branch used when omitted. That is format, source, and default behavior beyond the bare schema.

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 opens with a specific verb and resource ('Set verifAIed up for a repository') and makes the tool's role as the first-call orchestrator explicit by telling the agent to call it after connecting and again after each step. It stops short of naming sibling tools it supersedes, so differentiation is inferred from workflow position rather than stated directly.

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?

The calling cadence is unusually well specified: 'Call this first after the verifAIed MCP is connected, and again after each step,' plus follow-up guidance to run `verify` on `check_locally` steps. There are no explicit exclusions or named alternatives beyond that, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources