Skip to main content
Glama

docx-queryMeta

Retrieve metadata from a Word document by its ID. Access document properties and details programmatically.

Instructions

Get docx metadata by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • src/index.ts:49-52 (registration)
    Tool registration/definition for 'docx-queryMeta' in the tools dictionary with description and inputSchema.
    "docx-queryMeta": {
      description: "Get docx metadata by id.",
      inputSchema: { type: "object", required: ["id"], properties: { id: { type: "string" } } }
    },
  • Handler for 'docx-queryMeta' tool: parses args for 'id' and calls registry.queryMeta(id).
    case "docx-queryMeta": {
      const { id } = parseArgs<{ id: string }>(args, tools["docx-queryMeta"].inputSchema);
      return ok(registry.queryMeta(id));
    }
  • Input schema for 'docx-queryMeta' tool: requires 'id' (string).
    "docx-queryMeta": {
      description: "Get docx metadata by id.",
      inputSchema: { type: "object", required: ["id"], properties: { id: { type: "string" } } }
    },
  • The DocRegistry.queryMeta() method: retrieves the managed doc by ID and returns its id, createdAt, updatedAt, and meta object.
    queryMeta(id: DocId) {
      const cur = this.require(id);
      return {
        id: cur.id,
        createdAt: cur.createdAt,
        updatedAt: cur.updatedAt,
        meta: cur.json.meta ?? {}
      };
    }
Behavior2/5

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

No annotations exist, so the description carries full burden. It states 'Get' implying read-only, but does not disclose idempotency, error behavior (e.g., missing id), authorization needs, or response characteristics.

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 very brief (one sentence), which is concise but underspecified. It lacks essential details without being verbose. It earns a middle score for efficiency but insufficient content.

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?

Given the tool's simplicity (1 param, no output schema, no annotations), the description should provide enough context. It only mentions 'get metadata by id', omitting return format, field names, and error handling. Incomplete for reliable use.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning beyond the schema. The 'id' parameter is documented only as a string with no format, source, or required encoding explained.

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 ('docx metadata by id'), clearly indicating the action and object. It distinguishes from sibling tools like docx-editMeta (edit) and docx-queryObjects (query objects), but lacks specificity on what metadata entails.

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 on when to use this tool versus alternatives such as docx-queryObjects or docx-getSchema. The description does not mention prerequisites, context, or exclusion scenarios.

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

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