Skip to main content
Glama

Get Dataset Sample Tool

get-dataset-sample
Read-only

Return a small sample of recent rows from a dataset. User tables are ordered by record_time descending. System log tables are ordered by run_time or record_time descending. The default limit is 10 and the maximum is 50. The rows are a recent sample, not a population for statistics.

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-sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return. Defaults to 10 and is capped at 50.
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. Required when dataset_id is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only supply readOnlyHint, so the description carries the rest and does add real behavioral detail: ordering semantics differ between user tables (record_time desc) and system log tables (run_time or record_time desc), plus default and maximum limits. It stops short of describing error behavior (e.g. when neither dataset_id nor table_name is supplied) or row-shape.

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

Conciseness4/5

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

Front-loaded with the action, then ordering, then limits, then the sampling caveat — a sensible priority order. The limit sentence duplicates the schema description of the same parameter, which is minor waste.

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?

For a read-only tool with no output schema, the description tells the agent what comes back (recent rows, ordered, capped) and enough to call it correctly. Only edge-case behavior for the optional dataset_id/table_name pair is left unaddressed.

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 schema already documents the limit default/cap and the dataset_id-or-table_name requirement, so the description's limit sentence is largely redundant. It adds no syntax or format meaning beyond what the schema states; baseline 3 applies.

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?

States a specific verb and resource ('Return a small sample of recent rows from a dataset') and pins down the sampling scope. It implicitly separates itself from a full query tool by warning that rows are 'a recent sample, not a population for statistics', though it never names the alternative tool.

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?

Usage is only implied: the note that the sample is not suitable for statistics hints at when not to use it, but there is no explicit when-to-use condition and no named alternative such as run-query for full or aggregate retrieval.

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