Skip to main content
Glama
Sign In
grp-docx-mcp

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_tables

Retrieve all tables from a Word document, including row and column counts and cell text content.

Instructions

Get all tables with row/column counts and cell text content.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

B3.3/5.0
Behavior3/5

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

Discloses return value content (row/column counts, cell text), but with no annotations, it should also note that this is a read-only operation (implied by 'get') and warn about potential performance/large data volume. Does not mention empty document behavior.

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?

Single sentence, no redundant words. Could be slightly improved by front-loading the main action, but it's already concise. Loses 1 point for missing parameter clarification.

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?

Output schema exists but is not referenced. Input parameter unexplained. For a simple retrieval tool, basic purpose is clear, but additional context about data volume and alternatives would improve completeness.

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?

With 0% schema description coverage, the description fails to explain the sole parameter 'document_handle'. Its purpose, format, and effect are not mentioned, leaving the agent to infer from the name alone.

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?

Description uses specific verb 'Get' and specifies resource 'all tables'. It explicitly mentions the returned data (row/column counts and cell text content), clearly distinguishing this tool from sibling 'get_table' which suggests retrieving a single table.

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 vs alternatives like 'get_table' or other table-related tools. Description does not mention prerequisites, typical scenarios, or exclusions.

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

Deploy Server

Other Tools