Fetch a file's content from a workspace by supplying its ID and the file path, enabling direct access to repository files for review and collaboration.
Read a file's content from within an active workspace.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| workspace_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden of behavioral disclosure. It clearly indicates a non-destructive read operation and ties it to an active workspace, but it does not disclose error semantics, file-size limitations, or what happens when the requested path does not exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler or redundancy. It is concise, though slightly too terse given the presence of several closely related sibling tools.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, no annotations, and no parameter explanation, the description is the only source of contextual information. It does not help an agent choose between read_file, read_project_file, and read_change_file, nor does it explain how the return content is delivered. The tool may be callable, but the context is not sufficient for confident selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage and the description does not explain the workspace_id or path parameters beyond implying a workspace context. The parameter names are somewhat self-explanatory, but the description adds little real semantic value for agent invocation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action and resource: 'Read a file's content from within an active workspace.' However, it does not differentiate read_file from sibling read tools like read_project_file or read_change_file, so it cannot reach a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to use this tool versus siblings such as read_project_file, read_change_file, list_files, or search_files. The phrase 'active workspace' implies a condition, but there are no explicit when-to-use or when-not-to-use instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.