siliconsmith-mcp

Overview Schema Source Related Servers Discussions Admin

list_files

Read-only

Lists project files with relative paths and sizes in bytes while omitting symlinks, dotfiles, and build output unless include_build is enabled. Returns up to 500 files.

Instructions

List the files in a project (paths relative to the project folder, with sizes in bytes). Symlinks and dotfiles are never listed. Build output (build/, sim_build/) is hidden unless include_build is true. At most 500 files are returned.

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": {
      "project": "<project>"
    },
    "name": "list_files"
  }
}

Input Schema

Name	Required	Description	Default
`project`	Yes
`include_build`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`details`	No
`summary`	Yes
`artifacts`	No
`next_hints`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the behavioral load and does so well: it discloses that symlinks and dotfiles are never listed, that build/ and sim_build/ output is filtered by default, and that results are capped at 500 files. It stops short of saying whether the cap is signalled or how to page past it, which keeps it off a 5.

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?

Three short sentences, each carrying new information, with the core purpose and return format front-loaded and the filter and size caveats following. No padding or restatement of the tool name.

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

Completeness4/5

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

With an output schema present, return values need not be explained, and the safety profile is covered by annotations. What remains thin is ordering of results and the exact meaning of the project identifier for a recursive listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate: it defines include_build's effect precisely (reveals build/ and sim_build/) and implies that project scopes the relative paths. It does not clarify whether project is a name or a path, leaving one gap on the required parameter.

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?

States a specific verb and resource ("List the files in a project") plus the return shape (paths relative to the project folder, sizes in bytes). That is enough for an agent to distinguish it from read_file or inspect_waves without opening a schema.

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?

The description gives filtering rules and the include_build condition, which imply when this tool applies, but it never explicitly contrasts itself with read_file or says when not to use it. Usage is inferred rather than stated.

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

Deploy Server