Skip to main content
Glama
Sign In
Aztec MCP Server

Aztec MCP Server

Official
by AztecProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

aztec_sync_repos

Clone or update Aztec repositories locally for searching. Specify version and repos to sync.

Instructions

Clone or update Aztec repositories locally. Run this first to enable searching. Clones: aztec-packages (docs, aztec-nr, contracts), aztec-examples, aztec-starter. Specify a version to clone a specific Aztec release tag.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aztec_sync_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoAztec version tag to clone (e.g., 'v4.3.0'). Defaults to latest supported version.
forceNoForce re-clone even if repos exist (default: false)
reposNoSpecific repos to sync. Options: aztec-packages, aztec-examples, aztec-starter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided. Description covers cloning/updating and version specification but lacks details on update behavior (e.g., overwrite policy) and force flag effect. Adequate but not comprehensive.

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, front-loaded with core action and placement. No fluff. Earns its place.

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?

Given no output schema and simple params, description covers main purpose and usage order. Lacks what the tool returns (e.g., success message). Good but not fully comprehensive.

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?

Schema coverage is 100%, so baseline 3. Description adds minimal value beyond schema descriptions; e.g., explains version as release tag, force as re-clone. No additional constraints or examples.

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 verb (clone or update) and resource (Aztec repositories locally), and lists specific repos. It distinguishes from sibling tools focused on searching or reading.

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?

Explicit: 'Run this first to enable searching.' Indicates prerequisite status. Does not explicitly state when not to use or mention alternatives, but siblings are clearly different.

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