Skip to main content
Glama
Sign In
DOCX MCP Server

DOCX MCP Server

by Mavline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

docx.metadata_get

Retrieve document metadata by providing the document ID. Access core details such as title, author, and creation date to verify or extract essential information.

Instructions

Get document metadata

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": {
      "docId": "<docId>"
    },
    "name": "docx.metadata_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
docIdYesDocument ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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 of behavioral disclosure. The verb 'Get' implies a read-only operation, but the description does not state what metadata is returned, whether the operation has side effects, or what errors or prerequisites apply.

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

Conciseness3/5

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

The description is a single short sentence with no redundancy and the action is front-loaded. However, it is under-specified rather than usefully concise, providing no extra context beyond the tool name itself.

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

Completeness2/5

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

For a tool with no output schema and no annotations, the description should explain what metadata is returned and any operational context. It does neither, leaving an agent to guess at the return format and behavior beyond the basic 'get metadata' intent.

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%, and the single parameter docId is already described as 'Document ID'. The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Get') and resource ('document metadata'), which clearly indicates the tool's function. It is distinct from content-focused siblings like docx.get_text or docx.styles_get, though it does not explicitly name or contrast those alternatives.

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 is provided about when to use this tool versus other metadata-adjacent or read-only siblings. There is no mention of prerequisites, such as the document needing to be open, or any exclusions that would help an agent choose this tool over alternatives.

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