Skip to main content
Glama

Tessryx

by io.tessryx
OverviewDiscussionsAdmin

List datafiles

list_datafiles
Read-onlyIdempotent

List the datafiles belonging to the authenticated tenant. A datafile is a published JSON object served from a CDN — the data layer a page can fetch and hydrate from.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_sizeNomaximum number of datafiles to return in this page
page_tokenNotoken from a previous response's next_page_token to fetch the next page
slug_prefixNoonly return datafiles under this FOLDER path (matched on whole '/'-delimited segments, NOT as a raw string prefix), e.g. 'blog/posts' (trailing slash optional) returns everything under blog/posts/. A partial segment matches nothing — 'blog/2026-08' will NOT match 'blog/2026-08-01-hello'; use the full segment(s)
include_totalNoif true, also return total_count: the number of datafiles at this folder level (direct children of slug_prefix, or the tenant total when no prefix). Exact-as-full-total for a flat collection like a blog's posts under one prefix; a per-level count when nested. Use it for 'N items' / 'page X of Y'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
datafilesYes
total_countNo
next_page_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Behavioral annotations already cover read-only, idempotent, non-destructive, and closed-world semantics, so the bar is lower. The description adds context about tenant scoping and the CDN data-layer purpose without contradicting or overpromising side effects.

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?

The description is two tight sentences: the first states the operation and the second explains the domain concept. No filler or redundant wording is present.

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?

Given the low complexity, complete parameter schema, and existing output schema, the description supplies the needed domain context (what a datafile is and why it matters). It does not need to explain return values because the output schema already handles that.

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?

The input schema descriptions cover all four parameters at 100%, including page_size, page_token, slug_prefix, and include_total. The tool description does not add additional parameter-level meaning, so it stays at the baseline for high schema coverage.

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?

The description opens with 'List the datafiles belonging to the authenticated tenant', giving a specific verb and resource. It also defines datafile, which distinguishes it from other list_* tools and from get/create/delete datafile variants.

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?

The description provides useful context by defining a datafile as a published CDN JSON object, implying the tool is for enumerating that data layer. It does not explicitly name alternative tools or exclusions, but the context is clear enough for selection.

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

All Tessryx toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources