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

tool-mcp-server

by maple-awa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tool_image_preview

Preview images directly by providing their base64-encoded file data. View image details without opening external applications.

Instructions

[viewer] Image Preview

Parameters:

  • file (bytes): File

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_image_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoFile (base64 file payload)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of disclosing behavior. It does not state whether the image is displayed, returned, or validated, nor any side effects. The '[viewer]' prefix hints at a viewing role but provides no concrete behavior.

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 short, but every line wastes space: the title restates the name and the parameter list duplicates schema information with an incorrect type. It is under-specified rather than concise.

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?

There is no output schema, no annotations, and the description is a placeholder. Given the tool's potential role among many image tools, the description fails to provide even a minimal understanding of what 'preview' means or what the user can expect.

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 schema already covers the file parameter in detail (base64, filename, mimeType). The description's 'file (bytes): File' is not only redundant but misleading, as the schema defines an object, not raw bytes. This actively detracts from understanding.

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

Purpose1/5

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

The description 'Image Preview' is a noun phrase that merely restates the tool name. It lacks a specific verb or resource description, and does nothing to distinguish this tool from sibling image tools like tool_exif_viewer or tool_image_compress.

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 given on when to use this tool versus alternatives. The description contains no situational context, exclusions, or references to other tools.

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