Boarderless MCP Server

Standardize Images in Folder

graduation_standardize_images

Destructive

Converts progressive JPEGs and HEIC files to standard baseline RGB JPEGs in a local folder, returning a structured report of conversions and errors.

Instructions

Scan and convert progressive JPEGs and HEIC files inside subdirectories into standard baseline RGB JPEGs. Operates on the local filesystem — no browser required. Returns a structured report of converted files and any errors encountered.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "seniorsDir": "<seniorsDir>"
    },
    "name": "graduation_standardize_images"
  }
}

Input Schema

Name	Required	Description	Default
`seniorsDir`	Yes	Absolute path to the folder containing photos.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.28Jul 9, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations indicate destructiveHint=true, but the description only says 'convert' without clarifying whether original files are overwritten or new files are created. It does not add behavioral context beyond what annotations provide, and the ambiguity could mislead an agent about the impact.

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

Conciseness4/5

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

The description is two concise sentences with front-loaded action and resource. It covers input, operation, context, and output efficiently, though a slightly more structured format could improve scannability.

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 tool with one parameter, the description covers input, action, output (structured report), and context (subdirectories, local filesystem). It lacks details like handling of other formats or error scenarios, but is largely complete.

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 coverage is 100% and the single parameter already has a clear description ('Absolute path to the folder containing photos'). The tool description adds no additional meaning, so it meets the baseline without exceeding it.

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 description clearly states the tool scans and converts progressive JPEGs and HEIC files into standard baseline RGB JPEGs. The verb 'scan and convert' is specific, and the resource (images in subdirectories) is well-defined. It distinguishes from sibling tools like graduation_rename_photos which focuses on renaming.

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

Usage Guidelines3/5

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

The description mentions 'operates on the local filesystem — no browser required,' providing context for when to use it (local automation vs. browser-based tools). However, it does not explicitly state when not to use it or mention alternatives, leaving usage guidance somewhat implied.

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

Deploy Server