Skip to main content
Glama

get_cell_text

Retrieve the text from a specific cell in a Word document table by specifying 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
col_idxYes
row_idxYes
table_idxYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the return format and index details but does not disclose error behavior (e.g., out-of-bounds indices) or confirm read-only status. Adequate but could be more 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?

The description is extremely concise with a clear purpose statement and structured args/returns. Every sentence is necessary and front-loaded.

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?

Given the tool's simplicity, the description provides all necessary information: purpose, parameter semantics, and return structure. The output schema is documented, so no gaps remain.

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

Parameters5/5

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

Schema description coverage is 0%, but the description compensates fully by explaining each parameter's meaning (0-based indices) and the exact return format. This adds significant value beyond the schema types.

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?

The description clearly states the tool returns text content of a specific cell, using a specific verb and resource. It distinguishes from sibling tools like get_table, modify_cell, and set_cell_* by focusing on reading text content only.

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?

The description implies usage when reading cell text is needed but does not explicitly mention when not to use it or provide alternatives. The purpose is clear, but guidance is lacking given the many sibling tools with similar cell operations.

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/Arvindh95Censof/grp-docx-mcp'

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