Skip to main content
Glama

TweekIT MCP Server

by io.github.equilibrium-team

doctype

Retrieve a list of supported file formats or map a file extension to its document type.

Args: apiKey (str): The API key for authentication. Falls back to TWEEKIT_API_KEY when omitted. apiSecret (str): The API secret for authentication. Falls back to TWEEKIT_API_SECRET when omitted. extension (str): The file extension to query (e.g., 'jpg', 'pdf') or leave off or use '*' to return all supported input formats.

Returns: Dict[str, Any]: A dictionary containing the supported file formats or an error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyNoTweekIT API key passed via the ApiKey header. Defaults to the TWEEKIT_API_KEY environment variable when omitted.
apiSecretNoTweekIT API secret paired with the apiKey. Defaults to the TWEEKIT_API_SECRET environment variable when omitted.
extensionNoFile extension to inspect; use '*' to list all supported inputs.*

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It discloses read-only retrieval, API key/secret fallback to environment variables, and that the return is a dictionary of formats or an error message. It doesn't cover rate limits or exact error semantics, but for a simple lookup this is adequate.

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 front-loaded with a one-sentence purpose and uses a compact Args/Returns structure. It contains no filler and every section effectively contributes to understanding the tool.

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

Completeness4/5

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

For a simple 3-parameter lookup tool with a full schema and output schema, the description covers purpose, parameter semantics, auth fallback, and return behavior. It lacks explicit sibling comparisons, but is otherwise contextually sufficient.

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 schema already documents defaults and environment fallback. The description adds only examples like 'jpg' and 'pdf' and clarifies '*' behavior, which is marginal value over the structured data already available.

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

Purpose5/5

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

The opening sentence clearly states 'Retrieve a list of supported file formats or map a file extension to its document type,' providing a specific verb and resource. This distinguishes it from sibling conversion tools by focusing on type mapping and supported-format listing rather than conversion.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the extension argument's optionality and that '*' lists all formats, giving clear operational context. It doesn't explicitly name alternatives or when-not-to-use, but the behavior is clear enough for an agent to select it for mapping or listing document types.

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

All TweekIT MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

convert and convert_url are clearly differentiated by input source (blob vs URL), while doctype, fetch, and search serve distinct purposes. Minor overlap exists between convert_url and fetch (both fetch remote content), but the conversion vs. plain-fetch distinction is explicit in descriptions.

Naming Consistency3/5

Tool names use a mix of bare verbs (convert, fetch, search), verb_noun (convert_url), and a noun (doctype). The pattern is inconsistent, though all names are lowercase and readable.

Tool Count5/5

Five tools is a well-scoped set for a document conversion and URL retrieval server. Each tool addresses a distinct need without unnecessary redundancy.

Completeness4/5

Core workflows are covered: conversion from uploaded blobs and URLs, format discovery, and web retrieval/search. Minor gap: no explicit output format listing separate from input formats, but the convert tool's outfmt parameter covers it.

Resources