Skip to main content
Glama
Sign In
Aztec MCP Server

Aztec MCP Server

Official
by AztecProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

aztec_read_file

Access and read files from local Aztec repositories by specifying a relative path. Enables retrieval of documentation, source code, and examples for development or reference.

Instructions

Read any file from the cloned repositories by path. Path should be relative to the repos directory.

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": {
      "path": "<path>"
    },
    "name": "aztec_read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFile path relative to repos directory (e.g., 'aztec-packages/docs/docs/tutorials/...')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description fails to disclose behavioral traits such as read-only nature, potential side effects, or error handling (e.g., behavior if path is invalid), leaving the agent uninformed about important aspects.

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 a single sentence with no extraneous words, but could be structured to front-load key information like the tool's purpose more prominently.

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

Completeness3/5

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

Given the simple single-parameter tool with no output schema, the description is minimally adequate for a read operation, but it omits details about return values, error conditions, and potential limitations (e.g., large or binary files).

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?

Although schema coverage is 100% and the schema already describes the 'path' parameter with an example, the description adds no new meaning beyond restating 'relative to repos directory', earning a baseline score.

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 'Read' and the resource 'any file from the cloned repositories by path', effectively distinguishing it from sibling tools like aztec_search_code and aztec_list_examples by focusing on file content retrieval.

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 description provides clear guidance on path format ('relative to the repos directory') but does not explicitly list when to use this tool versus alternatives like aztec_search_code for searching file contents.

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