Skip to main content
Glama

office_modernize_legacy

Convert legacy .doc, .xls, and .ppt files into modern .docx, .xlsx, and .pptx formats, enabling current Office tools to open and edit older documents.

Instructions

Modernize legacy Office document. [Input: Legacy Office (.doc, .xls, .ppt) | Output: Modern Office (.docx, .xlsx, .pptx)]

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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "office_modernize_legacy"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it says nothing about overwrite behavior, whether 'output' must be a new path, permission/auth requirements, or fidelity loss during upgrade (e.g. macros, embedded objects). Only the format mapping is disclosed.

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?

Two short, front-loaded clauses with a clear Input/Output split and zero filler. The bracket shorthand is slightly cryptic but efficient.

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?

A two-required-parameter conversion tool with no annotations, no output schema, and 0% parameter coverage leaves key gaps: the nature of the path arguments and the success/failure result are unspecified. The description does not compensate for that missing structure.

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?

Schema coverage is 0%, so both required parameters are undocumented. The bracket notation maps formats onto input and output, which adds a little meaning, but it never clarifies whether the values are filesystem paths, base64 payloads, or URLs, nor what happens if extensions mismatch.

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?

States a specific verb and resource ('Modernize legacy Office document') and pins the transformation direction with concrete extensions (.doc/.xls/.ppt -> .docx/.xlsx/.pptx). An agent can tell it is a format-upgrade converter, though it does not name a sibling it is distinct from (e.g. office_to_markdown or excel_to_csv).

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 when-to-use or when-not-to-use guidance is given. Nothing says whether to pick this over office_extract_text, office_to_markdown, or excel_to_csv, nor whether it handles one file or a batch.

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