Skip to main content
Glama
Sign In
tool-mcp-server

tool-mcp-server

by maple-awa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tool_office_viewer

View office documents by providing a file to extract structured information. This tool accepts base64 file content and returns JSON details about the file.

Instructions

[viewer] Office Viewer

Parameters:

  • file (bytes): File

Outputs:

  • info (json): Info

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": "tool_office_viewer"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoFile (base64 file payload)
infoNoInfo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states 'File' as input and 'Info' as output, offering no details on what processing occurs, what information is extracted, or any side effects. This is completely opaque.

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

Conciseness2/5

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

The description is extremely short, but the brevity stems from under-specification rather than refined conciseness. It lists parameters and outputs in a structured format, but every sentence is essentially a placeholder that fails to convey meaningful content.

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

Completeness1/5

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

For a tool that likely handles complex office document formats, the description is severely incomplete. It provides no information on supported file formats, output structure, error handling, or security considerations. There is no output schema to compensate, and the input schema's nested 'file' object is not explained.

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?

The description merely repeats the schema property names ('file', 'info') without adding explanation. Worse, it labels 'info' as an output while the input schema includes it as a property, creating ambiguity about the actual input/output contract. The schema descriptions are minimal ('Info'), and the description does not clarify.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially a title with 'Office Viewer' and a list of parameters/outputs, but lacks a clear verb-resource statement. It does not explain what 'viewing' an office file entails or differentiate itself from sibling tools like tool_exif_viewer or tool_json_preview.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 vs alternatives. There is no mention of supported file types, prerequisites, or situations where another tool would be more appropriate.

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