Skip to main content
Glama

get_cell_text

Extract text from any cell in a Word document table by specifying the zero-based indices for table, row, and column.

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
Behavior2/5

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

No annotations are provided, and the description does not disclose whether the tool is read-only or has side effects. It only states the return value, missing critical behavioral context for an AI agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise with clear Args/Returns sections. Front-loaded purpose. No wasted words, but could be slightly more informative without lengthening.

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

Completeness3/5

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

Covers the basic function and return format, but lacks usage guidelines and behavioral transparency. For a simple read tool, it is adequate but not fully comprehensive given the tool's context in a rich document manipulation server.

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?

The description adds '0-based index' for each parameter, which is absent from the input schema. With schema coverage at 0%, this clarifies the indexing convention, though it could specify valid ranges or defaults.

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 action ('return') and resource ('text content of a specific cell'), exactly matching the tool's function. It is distinct from sibling tools like modify_cell or set_cell_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., get_body_text, modify_cell). The description does not mention when it is appropriate or what constraints apply.

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