List files in the MS-MCP workspace root or subdirectory to view available modeling inputs and results. Enables checking job files and outputs for analysis.
List files under the MS-MCP work root.
| Name | Required | Description | Default |
|---|---|---|---|
| subdir | No | . | |
| maxFiles | No |
Changes observed during successful MCP inspections.
v0.2.0-hardened.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only states 'list files' without indicating if the operation is read-only, has side effects, or requires authentication. The lack of transparency is significant for a tool with no annotations.
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 short sentence, which is concise, but it sacrifices necessary detail. It is under-specified for an effective tool description, though no redundant information is present.
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?
Given the tool complexity (2 parameters, no output schema, no annotations), the description is incomplete. It does not explain parameter usage, return format, or filtering behavior, leaving the agent without crucial information for correct invocation.
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?
Schema description coverage is 0%, meaning parameters have no descriptions. The tool description does not mention parameters at all, providing no additional meaning for 'subdir' or 'maxFiles'. The agent cannot infer their semantics from the description.
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 clearly states the tool lists files under the MS-MCP work root, providing a specific verb and resource. It is not a tautology and distinguishes from siblings like ms_status or ms_gui_project_dir. However, it lacks detail on whether directories are included or recursion behavior.
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 on when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.