Skip to main content
Glama
Sign In
krexel-mcp

krexel-mcp

by Syfer-web
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_files

List files in a deployed site to view file paths, sizes, and SHA256 hashes. Get metadata without downloading content.

Instructions

List the files in a deployed site (paths, sizes, sha256). Returns metadata only — use read_file to fetch content.

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

Input Schema

NameRequiredDescriptionDefault
deploy_idYesThe deploy_id returned from ship_site (or any patch deploy).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses return type (metadata) and what it does not do (fetch content). Missing details on pagination, error handling, or permission requirements.

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?

Two sentences, front-loaded with action and result, then key distinction. No waste.

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?

Simple tool with one parameter and no output schema. Description provides essential purpose and return type, but could detail the structure of the returned objects more explicitly.

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 has 100% coverage with a description of deploy_id. Tool description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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?

Description clearly states the tool lists files in a deployed site with specific metadata (paths, sizes, sha256). It distinguishes from read_file by noting it returns metadata only.

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 via mention of read_file for content, but no explicit when-to-use vs other siblings like list_deploys or get_status. Lacks guidance on prerequisites or context.

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