Skip to main content
Glama

get_data_table_record

Read-onlyIdempotent

Get one record by recordKey. Response includes version for optimistic locking on update_data_table_record. Use when reading a single row before updating it.

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": {
      "dataTableId": "<dataTableId>",
      "recordKey": "<recordKey>"
    },
    "name": "get_data_table_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordKeyYesBusiness key unique within the table
dataTableIdYesData table id

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only and idempotent behavior, so the description's added value is the disclosure that the response includes a version field used for optimistic locking. That is real workflow context an agent cannot get from the structured fields, though nothing is said about not-found behavior.

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 core action, and every sentence contributes either the lookup scope, the return content, or the usage trigger.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read with full schema coverage and no output schema, the definition supplies everything needed: what to pass, what comes back (version), and the scenario that selects it.

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 both parameters are already fully documented. The phrase 'by recordKey' merely restates the schema and adds no format, casing, or scoping detail beyond it, so the baseline applies.

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?

States a specific verb and resource ('Get one record') plus the lookup key ('by recordKey'), which separates it from list_data_table_records and get_data_table without needing either schema opened.

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?

'Use when reading a single row before updating it' gives an explicit trigger and names the successor tool (update_data_table_record). It doesn't state the inverse case (e.g. use list_data_table_records when you don't have a recordKey), but the selection context is clear.

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