Skip to main content
Glama

Get Dataset Metadata Tool

get-dataset-metadata
Read-onlyIdempotent

Return architecture metadata, column schema, and manager-only load settings for one dataset. Pass dataset_id or table_name. Load settings are null unless the user is a manager of that table. System log tables return a guidance message instead of a schema.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-dataset-metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceNoSpace slug. Required when the token is bound to more than one space. Omit it when the token has one space.
dataset_idNoNumeric dataset id. Required when table_name is omitted.
table_nameNoPhysical table name, including system tables such as dl_trans_runs. Required when dataset_id is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and idempotentHint, so the safety profile is already known. The description adds two non-obvious behaviors that annotations cannot express: load settings are null unless the caller manages the table, and system log tables return a guidance message instead of failing. It does not cover error behavior for an unknown dataset_id or table_name, which keeps it below a 5.

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?

Three short sentences, front-loaded with the return payload, followed by the identifier rule and the two special cases. Every sentence carries distinct information and nothing is repeated from the schema.

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?

With no output schema, the description carries the burden of describing return values, and it does so concisely while flagging the manager-only field and the system-table special case. What is missing is failure/lookup behavior when neither identifier resolves to a dataset, a small gap for a three-parameter read tool.

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%, so each parameter including the space slug is already documented, and the baseline is 3. The description restates the dataset_id/table_name either-or rule and adds nothing about the space parameter or what a physical table name looks like beyond the schema's own example.

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

Purpose4/5

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

The description uses a specific verb and resource and enumerates exactly what comes back: architecture metadata, column schema, and manager-only load settings for a single dataset. That is far more informative than the title. It stops short of differentiating from the closest sibling, get-dataset-sample, which also targets a dataset.

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?

It gives a clear selection rule between the two identifier parameters (dataset_id or table_name) and discloses that system log tables yield guidance rather than a schema. It never states when to prefer this tool over get-dataset-sample or list-datasets, so the usage context is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources