Skip to main content
Glama
Sign In
maic-server-fs-mcp

maic-server-fs-mcp

by maicFir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

readFile

Read the content of a local file at a specified path, enabling AI to access and view file code or text.

Instructions

读取指定路径的本地文件内容，允许 AI 查看文件代码或文本。

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": {
      "filePath": "<filePath>"
    },
    "name": "readFile"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYes相对或绝对路径，例如 'package.json' 或 'src/index.js'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only states the basic operation without disclosing error handling, permissions, or encoding assumptions.

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?

Single sentence, concise and front-loaded. Could be slightly more informative without becoming verbose.

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?

Adequate for a simple read tool, but lacks details on output format, encoding, or potential errors. No output schema to compensate.

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% with a clear description and example; the tool description adds no extra meaning beyond what the schema already provides.

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 tool reads file content from a local path, and is distinct from sibling tools like writeFile (write) and readDirectory (list).

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?

Implied usage for viewing file content, but no explicit when-to-use or when-not-to-use guidance relative to alternatives like readDirectory or searchCodebase.

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