Skip to main content
Glama

sample_table

Read-onlyIdempotent

Retrieve a small synthetic row sample from a table or workspace to preview data and validate schemas without querying full datasets.

Instructions

Return a small synthetic sample of rows from a table.

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": {
      "table": "<table>"
    },
    "name": "sample_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNoNumber of rows (1-50).
tableYes
workspaceNoNamed workspace. Omit to use the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the useful traits 'small' (bounded output) and 'synthetic sample', but does not clarify whether the sample is deterministic across calls (which idempotentHint would imply) or how large the underlying table can be without affecting sampling.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity borders on under-specification for a three-parameter tool.

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

Completeness3/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 could have said what shape the returned rows take and whether synthetic values are fabricated or drawn from stored data — a critical distinction for an agent that might use the result as real data. The annotations cover safety, but the description is thin on semantics for a tool whose output is its whole purpose.

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 coverage is 67%, and the description does nothing to compensate for the undocumented 'table' parameter — it never says whether the table must already exist, what identifier form it takes, or how it relates to the workspace parameter. 'Sample of rows' only loosely echoes the 'rows' parameter, which the schema already fully documents.

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 ('Return a small synthetic sample of rows from a table'), which is distinct from sibling operations like describe_table or list_tables. What 'synthetic' means (generated placeholder data vs. a random subset of real rows) is left ambiguous, but the core operation is clear.

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

Usage Guidelines2/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 rather than describe_table, list_tables, or vector_search, and no prerequisites or exclusions are stated. The agent must infer usage entirely from the name and one-sentence description.

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