Skip to main content
Glama

get_supported_formats

Lists supported Microsoft Office file formats and extensions for conversion to Markdown, including Word, Excel, and PowerPoint documents.

Instructions

Get list of all supported file formats.

Returns a dictionary of file types (word, excel, powerpoint) and their extensions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler for the 'get_supported_formats' tool call. Returns a JSON response containing the supported formats dictionary and a list of all extensions.
    elif name == "get_supported_formats":
        return [TextContent(
            type="text",
            text=json.dumps({
                "supported_formats": SUPPORTED_FORMATS,
                "all_extensions": get_supported_extensions(),
            }, ensure_ascii=False, indent=2)
        )]
  • Registers the 'get_supported_formats' tool in the MCP server with its name, description, and empty input schema (no parameters required).
            Tool(
                name="get_supported_formats",
                description="""Get list of all supported file formats.
    
    Returns a dictionary of file types (word, excel, powerpoint) and their extensions.""",
                inputSchema={
                    "type": "object",
                    "properties": {},
                },
            ),
        ]
  • The input schema for the tool, which is an empty object since no parameters are needed.
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • Core data structure defining the supported file formats by category, imported and used directly by the tool handler.
    SUPPORTED_FORMATS = {
        "word": [".docx", ".doc"],
        "excel": [".xlsx", ".xls"],
        "powerpoint": [".pptx", ".ppt"],
    }
  • Helper function that flattens all supported extensions into a single list, used in the tool's response.
    def get_supported_extensions() -> list[str]:
        """Get list of all supported file extensions."""
        extensions = []
        for exts in SUPPORTED_FORMATS.values():
            extensions.extend(exts)
        return extensions
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the return format ('dictionary of file types... and their extensions'), it doesn't address important behavioral aspects like whether this is a cached operation (relevant given the 'clear_cache' sibling), whether it requires authentication, rate limits, or error conditions. The description provides basic output information but lacks comprehensive behavioral context.

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 perfectly concise and well-structured. The first sentence states the core purpose, and the second sentence provides essential output details. Every sentence earns its place with no wasted words, and the information is front-loaded appropriately for quick understanding.

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

Completeness3/5

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

Given the tool's simplicity (no parameters, no output schema, no annotations), the description is reasonably complete for a basic lookup tool. It explains what the tool does and what it returns. However, without annotations or output schema, it could benefit from more detail about the return structure (e.g., format of the dictionary, whether it includes MIME types) and behavioral context about caching or performance characteristics.

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

Parameters4/5

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

The tool has zero parameters (schema coverage 100%), so there are no parameters to document. The description appropriately doesn't waste space discussing nonexistent parameters. According to the scoring rules, zero parameters warrants a baseline score of 4, as there's nothing to compensate for and no unnecessary parameter discussion.

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 tool's purpose: 'Get list of all supported file formats.' This specifies the verb ('Get') and resource ('supported file formats'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_conversions' or 'get_document_metadata', which prevents a perfect score.

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. With sibling tools like 'list_conversions' and 'get_document_metadata' available, there's no indication of when this specific tool is appropriate versus those other options. The description simply states what it does without contextual usage information.

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/Asunainlove/OfficeReader-MCP'

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