Skip to main content
Glama
Sign In
DPF

DPF

by dpf-admin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List data specs or jobs

list_data
Read-onlyIdempotent

List data specs (parsing/mapping rule sets) or their processing jobs in a workspace. Supports pagination; for live Iceberg tables, submit a SHOW TABLES query instead.

Instructions

List either the data specs (parsing + mapping rule sets, resource "specs") or the data processing jobs (executions of a spec, resource "jobs") defined in a workspace. Paginated (default 25/page, max 100, newest first); pass the returned nextCursor to fetch more. Not a table listing — for the live set of Iceberg tables in a workspace, use submit_query with SHOW TABLES instead.

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": {
      "resource": "<resource>"
    },
    "name": "list_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque nextCursor from a prior page (omit for the first page).
pageSizeNoRecords per page (default 25).
resourceYesWhich kind of resource to list
workspaceIdNoWorkspace to act on. Defaults to your only workspace if you have exactly one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds context about pagination and ordering, which goes beyond annotations, but does not introduce additional behavioral caveats. Overall, it sufficiently complements the annotations.

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 concise, using two sentences to convey the primary purpose, pagination details, and a key distinction from a sibling tool. It is well-structured, starting with the core functionality and then adding supporting details and alternative references.

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?

Given the lack of an output schema, the description adequately covers the tool's actions, parameters, and pagination. It does not address potential errors or permissions, but these are not required for a simple listing operation. The description is complete enough for typical usage.

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?

The schema already describes all parameters, but the description adds meaningful context by explaining what 'specs' and 'jobs' represent (parsing/mapping rule sets vs. executions). It also clarifies the pagination mechanism, reinforcing the parameter descriptions without redundancy.

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 clearly states that the tool lists either data specs or data processing jobs, with brief definitions of each. It also explicitly contrasts with a sibling tool for table listing, leaving no ambiguity about the tool's purpose.

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

Usage Guidelines5/5

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

It provides explicit guidance on when to use this tool versus alternatives, such as using submit_query for live table listings. Pagination instructions (default page size, max, and cursor usage) are also clearly stated, covering practical usage scenarios.

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