Skip to main content
Glama
Sign In
ds-web-mcp

ds-web-mcp

by Ghubuserpym
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Look up DeepSeek file metadata

list_files
Read-only

Fetch server-side metadata for uploaded file IDs to confirm upload completion or re-check status before attaching files.

Instructions

Fetch the server-side metadata for previously uploaded file ids (name, size, mime type, upload status, content-audit verdict). Use to confirm an upload finished or to re-check status before attaching it.

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

Input Schema

NameRequiredDescriptionDefault
fileIdsYesFile ids returned by upload_files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so safety is already covered. The description adds useful behavioral context by listing exactly what metadata is returned, including upload status and content-audit verdict, which helps the agent understand the response shape.

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 compact sentences, front-loaded with the action and resource, and the second sentence provides usage context without repetition or filler.

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

Completeness5/5

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

For a simple read-only lookup with one fully documented parameter and annotation-covered safety, the description is complete. It also compensates for the absence of an output schema by naming the returned metadata fields.

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?

Schema coverage is 100% and the single fileIds parameter is already documented as coming from upload_files. The description reinforces that these are previously uploaded file ids, but adds little meaning beyond the schema.

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: fetch server-side metadata for previously uploaded file ids. It also names the exact metadata fields returned, which clearly distinguishes it from the upload_files sibling.

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

Usage Guidelines4/5

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

Explicitly says to use it to confirm an upload finished or re-check status before attaching. This gives clear use context, though it does not name explicit exclusions or alternative tools beyond the implied upload_files relationship.

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