Skip to main content
Glama

get_cell_text

Retrieve text content from a specific cell in a Word document table by providing table, row, and column indices.

Instructions

Return text content of a specific cell.

Args: table_idx: 0-based table index. row_idx: 0-based row index. col_idx: 0-based column index.

Returns: {"table_index": int, "row_index": int, "col_index": int, "text": str}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_idxYes
row_idxYes
col_idxYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. Describes return format but does not disclose error behavior (e.g., out-of-bounds indices, empty cells) or side effects. Adequate but not fully transparent.

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?

Extremely concise: one sentence for purpose, clear Args and Returns sections. Front-loaded and every word adds value. No fluff.

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 read tool with output schema provided, the description covers core functionality and parameter meaning. Lacks edge case handling but is sufficient for typical use. Could mention expected behavior when cell is empty.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% coverage (no descriptions). The description adds 0-based indexing semantics for each parameter, which is essential information not captured in the schema. Compensates well for the gap.

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?

Clearly states it returns text content of a specific cell with 0-based indices. Distinguishes from siblings like get_table (returns entire table) and modify_cell (changes data).

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?

Provides clear context on what the tool does but no explicit when-to-use or alternatives. The purpose is self-explanatory for reading a single cell, but lacks exclusion guidance compared to get_tables.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SecurityRonin/docx-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server