Skip to main content
Glama

file_read

Read file contents from remote servers, including code, logs, and configuration files. Use the tail parameter to fetch only the last N lines of large log files.

Instructions

读取远程服务器上的文件内容。支持文本文件(代码、日志、配置等)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes远程文件的绝对路径
tailNo仅读取最后 N 行(类似 tail -n),适用于日志文件
serverYes目标服务器名称
Behavior2/5

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

没有 annotations,描述承担全部行为披露责任。除'支持文本文件'外,未说明二进制文件处理、文件编码、大小限制、输出格式或权限要求;'读取'虽暗示只读,但未显式声明副作用或边界行为。

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?

描述仅两句话,首句直接点明核心功能,第二句补充支持的文件类型,没有冗余内容。信息密度高且结构清晰。

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

Completeness2/5

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

工具没有 output schema 且没有 annotations,仅有简短描述,缺少返回内容、失败条件、权限要求等上下文。sibling tools 中的 file_write、file_search 等需要说明边界,当前描述不足以让 agent 完整判断调用场景。

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?

input schema 覆盖了全部 3 个参数(server、path、tail)且每个都有描述,覆盖率 100%。描述没有在 schema 之外增加参数含义,'支持文本文件'与 tail 的日志场景略有关联,但未提供额外参数语义。

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?

描述明确说明'读取远程服务器上的文件内容',动词和资源清晰,并补充了支持文本文件类型。虽然未显式区分 file_list、file_search、file_write 等 sibling tools,但'读取'这一核心语义已足够明确。

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

Usage Guidelines2/5

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

描述没有说明何时使用 file_read 而非 file_search、file_list 或 server_exec,也未提及 tail 参数的使用场景(虽然 schema 中有)。仅通过'读取文件'暗示用途,缺少工具选择相关的指导。

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rowanlin-dev/cloud-ops-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server