Skip to main content
Glama

sp_read_table

Read-only

Read physical HTML table cells while preserving rowspan and colspan, without inferred interpretation. Use a snapshot ID and table index from the document outline to page through rows by offset.

Instructions

Read physical HTML table cells preserving rowspan/colspan; no inferred interpretation. Locate table_index using document_outline. Row offsets are zero-based.

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": {
      "snapshot_id": "<snapshot_id>",
      "table_index": "<table_index>"
    },
    "name": "sp_read_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
row_offsetNo
snapshot_idYes
table_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavioral context by saying cells are physical and rowspan/colspan are preserved with no inference, but it says nothing about pagination behavior, truncation when limit is hit, or what happens if row_offset exceeds the table.

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, front-loaded with the core capability and followed by the two operational facts an agent needs. No filler or redundancy.

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

Completeness2/5

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

With no output schema and 0% schema coverage on four parameters, the description leaves the return shape (how cells are represented, how spans are encoded) and the limit/snapshot_id semantics unexplained. It is adequate for identifying the tool but thin for invoking it correctly.

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 description coverage is 0% across 4 parameters, so the description must carry the load. It clarifies where table_index comes from (document_outline) and that row_offset is zero-based, but never explains snapshot_id, limit, or the default page size of 20.

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 ('Read physical HTML table cells') plus a scope qualifier ('no inferred interpretation') that distinguishes it from interpreted readers like document or clause readers. It is clear what the tool does, though it never names a sibling explicitly.

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?

Provides one real prerequisite ('Locate table_index using document_outline') and a note that row offsets are zero-based, which is actionable. It does not say when to prefer this over sp_read_document or sp_read_clause, so the choice between table-level and document-level reads is left to inference.

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