Skip to main content
Glama

get_data_table

Read-onlyIdempotent

Get one Persistent Data Table by id, including its typed field schema. Use when inspecting or editing a table before working with records.

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": {
      "id": "<id>"
    },
    "name": "get_data_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesData table id

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds value beyond them by disclosing that the response includes the typed field schema, which is precisely what an agent needs to know before editing. It omits error behavior for an unknown id, keeping 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?

Two short sentences, zero filler. The core action and returned content come first, and the usage condition follows, so nothing needs to be re-read.

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 simple single-parameter read tool with annotations and no output schema, the definition covers what it returns at a high level and when to reach for it. Only the failure case (invalid or missing id) is left implicit, which is a minor gap at this complexity.

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?

There is a single required parameter with 100% schema description coverage ('Data table id'), so the schema already carries the semantics. The description's 'by id' phrasing is consistent but adds no format, sourcing, or lookup detail beyond it, which is the baseline for fully covered parameters.

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 states a specific verb and resource ('Get one Persistent Data Table by id') and names the returned payload ('including its typed field schema'), which separates it from list_data_tables and the record-level siblings. It stops short of explicitly contrasting itself with get_data_table_record, so it is clear but not fully self-differentiating.

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?

It gives a concrete usage context: inspect or edit a table before working with records. That tells an agent the intended ordering relative to record operations. It does not state exclusions (e.g., 'do not use to fetch records, use get_data_table_record'), so it remains at clear-context level rather than full when/when-not routing.

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