Skip to main content
Glama
hedging8563

TokenLab MCP Server

by hedging8563
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List files

list_files
Read-onlyIdempotent

Retrieve a paginated list of files, filterable by purpose (batch, user data, vision) and cursor-based pagination. Use for managing stored uploads.

Instructions

List files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNo
limitNo
purposeNoOptional file purpose filter. batch and batch_output cover Batch API files; user_data and vision co…
after_idNoAnthropic Files cursor. Return files after this public file id. Requires the Anthropic Files beta h…
scope_idNoReserved Anthropic Files scope cursor. TokenLab currently returns an explicit unsupported error rat…
before_idNoAnthropic Files cursor. Return files before this public file id. Requires the Anthropic Files beta …
anthropic-betaNoInclude files-api-2025-04-14 to use Anthropic Files API mode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.24
    • changedInput schema / properties / after_id / description
      Previous value: -"Anthropic Files cursor. Return files after this public file id. Requires the Anthropic Files beta header and cannot be combined with before_id."New value: +"Anthropic Files cursor. Return files after this public file id. Requires the Anthropic Files beta h…"
    • changedInput schema / properties / before_id / description
      Previous value: -"Anthropic Files cursor. Return files before this public file id. Requires the Anthropic Files beta header and cannot be combined with after_id."New value: +"Anthropic Files cursor. Return files before this public file id. Requires the Anthropic Files beta …"
    • changedInput schema / properties / purpose / description
      Previous value: -"Optional file purpose filter. batch and batch_output cover Batch API files; user_data and vision cover TokenLab image/reference file bindings. Anthropic Files API mode is selected by Anthropic headers rather than this query parameter."New value: +"Optional file purpose filter. batch and batch_output cover Batch API files; user_data and vision co…"
    • changedInput schema / properties / scope_id / description
      Previous value: -"Reserved Anthropic Files scope cursor. TokenLab currently returns an explicit unsupported error rather than silently ignoring this value."New value: +"Reserved Anthropic Files scope cursor. TokenLab currently returns an explicit unsupported error rat…"
  2. Changed7 schema fields changedv0.6.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / after_id
      Added value: +{
+  "description": "Anthropic Files cursor. Return files after this public file id. Requires the Anthropic Files beta header and cannot be combined with before_id.",
+  "type": "string"
+}
    • addedInput schema / properties / anthropic-beta
      Added value: +{
+  "description": "Include files-api-2025-04-14 to use Anthropic Files API mode.",
+  "type": "string"
+}
    • addedInput schema / properties / before_id
      Added value: +{
+  "description": "Anthropic Files cursor. Return files before this public file id. Requires the Anthropic Files beta header and cannot be combined with after_id.",
+  "type": "string"
+}
    • addedInput schema / properties / limit / default
      Added value: +20
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +1000
    • addedInput schema / properties / scope_id
      Added value: +{
+  "description": "Reserved Anthropic Files scope cursor. TokenLab currently returns an explicit unsupported error rather than silently ignoring this value.",
+  "type": "string"
+}
  3. Addedv0.3.1

TDQS

D1.5/5.0
Behavior1/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds zero behavioral context — no mention of pagination/cursor semantics, the beta header requirement, or the fact that scope_id currently returns an unsupported error. It contributes nothing beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two words is not conciseness but under-specification; there is no front-loaded information because there is no information beyond the title restated.

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

Completeness1/5

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

For a tool with 7 parameters, cursor-based pagination, a beta-mode header, and a deliberately unsupported scoped cursor, the description is completely inadequate. An agent cannot call this correctly from the description alone.

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

Parameters2/5

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

Schema description coverage is 71%, so several parameters (after, limit) are undocumented even in the schema, and the description supplies no parameter meaning at all. It does not compensate for the coverage gap on a 7-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus the many file-related siblings, no mention of the Anthropic Files beta mode requirement, and no exclusions or prerequisites stated anywhere.

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