Skip to main content
Glama
kazuph
by kazuph

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_FETCH_TIMEOUT_MSNoRequest timeout in milliseconds12000
MCP_FETCH_MAX_REDIRECTSNoMaximum number of redirects to follow3
MCP_FETCH_MAX_HTML_BYTESNoMaximum HTML response size in bytes2000000
MCP_FETCH_MAX_IMAGE_BYTESNoMaximum image response size in bytes10000000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
resources
{
  "subscribe": true,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
imageFetchA

画像取得に強いMCPフェッチツール。記事本文をMarkdown化し、ページ内の画像を抽出・最適化して返します。

新APIの既定(imagesを指定した場合)

  • 画像: 取得してBASE64で返却(最大3枚を縦結合した1枚JPEG)

  • 保存: しない(オプトイン)

  • クロスオリジン: 許可(CDN想定)

パラメータ(新API)

  • url: 取得先URL(必須)

  • images: true | { output, layout, maxCount, startIndex, size, originPolicy, saveDir }

    • output: "base64" | "file" | "both"(既定: base64)

    • layout: "merged" | "individual" | "both"(既定: merged)

    • maxCount/startIndex(既定: 3 / 0)

    • size: { maxWidth, maxHeight, quality }(既定: 1000/1600/80)

    • originPolicy: "cross-origin" | "same-origin"(既定: cross-origin)

  • text: { maxLength, startIndex, raw }(既定: 20000/0/false)

  • security: { ignoreRobotsTxt }(既定: false)

旧APIキー(enableFetchImages, returnBase64, saveImages, imageMax*, imageStartIndex 等)は後方互換のため引き続き受け付けます(非推奨)。

Examples(新API) { "url": "https://example.com", "images": true }

{ "url": "https://example.com", "images": { "output": "both", "layout": "both", "maxCount": 4 } }

Examples(旧API互換) { "url": "https://example.com", "enableFetchImages": true, "returnBase64": true, "imageMaxCount": 2 }

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined and distinct.

Naming Consistency5/5

The single tool name 'imageFetch' is descriptive and follows a verb_noun pattern. There is no inconsistency since only one tool exists.

Tool Count4/5

While the server has only one tool, it is a complex and well-documented tool that handles a wide range of functionality appropriate for its fetch-image purpose. The count is slightly below the typical range but not insufficient.

Completeness5/5

The tool comprehensively covers fetching web pages, extracting images, and outputting them in various formats (base64, file, merged, individual). It includes parameters for text extraction and security, leaving no apparent gaps for its stated purpose.

Maintenance

ActivityInactive
ResponsivenessSlow