Docsmith MCP

Overview Schema Source Related Servers Discussions Admin

get_document_info

Extract document metadata including page count, sheet count, slide count, and file size from Excel, Word, PDF, and text files to analyze document structure and properties.

Instructions

Get document metadata (page count, sheet count, slide count, file size, etc.)

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": {
      "file_path": "<file_path>"
    },
    "name": "get_document_info"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes	Absolute path to the document file
`file_type`	No	Override file type detection (optional). Specify format explicitly instead of relying on extension

Output Schema

Name	Required	Description	Default
`error`	No
`pages`	No
`sheets`	No
`slides`	No
`tables`	No
`headers`	No
`success`	No
`encoding`	No
`metadata`	No
`file_size`	No
`file_type`	No
`key_count`	No
`item_count`	No
`line_count`	No
`paragraphs`	No
`total_cols`	No
`total_rows`	No
`total_words`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.3Feb 18, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Get document metadata' which implies a read-only operation, but doesn't disclose behavioral traits like error handling (e.g., if file doesn't exist), performance considerations, or authentication needs. The description is minimal and lacks context beyond the basic action.

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 a single, efficient sentence with zero waste. It's front-loaded with the core purpose and includes helpful examples (page count, etc.) that add value without verbosity.

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?

Given the tool's low complexity (simple metadata retrieval), 100% schema coverage, and the presence of an output schema (which handles return values), the description is reasonably complete. It clearly states what the tool does, though it lacks usage guidelines and behavioral details that could enhance agent understanding.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds no parameter-specific information beyond implying metadata retrieval, which is covered by the tool's purpose. Baseline 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the verb 'Get' and the resource 'document metadata' with specific examples (page count, sheet count, slide count, file size, etc.). It distinguishes from sibling tools like 'read_document' (which likely reads content) and 'write_document' (which modifies content), though it doesn't explicitly mention these distinctions.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., file existence), when not to use it, or how it differs from siblings like 'read_document' beyond the metadata focus implied in the purpose.

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

Deploy Server