Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

Skill: image optimization

get_skill_image_optimization
Read-onlyIdempotent

For agents with a local filesystem: resize and convert the user's image files to webp with the provided script BEFORE uploading them with upload_asset. Chat assistants without files should skip this and pass the image to upload_asset directly.

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": "get_skill_image_optimization"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world, so the description does not need to carry the full safety burden. The description adds useful behavioral context: a local filesystem prerequisite, the pre-upload ordering constraint, and a skip condition for chat assistants. It still leaves somewhat unclear whether the tool returns a script or instructions and how the script is provided.

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 two short sentences with no wasted language. The primary applicability condition is front-loaded, followed by the key action and skip alternative.

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 zero-parameter skill tool with no output schema, the description gives enough context to decide applicability and sequencing relative to upload_asset. It is slightly incomplete about what the caller receives, such as whether it returns a script, a path, or textual guidance, but the core workflow is clear.

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?

There are zero parameters, so the baseline is 4 according to the rubric. The description does not need to explain parameter meaning, and the schema is empty with full coverage.

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 states a specific image-related purpose: resize and convert the user's image files to webp before uploading via upload_asset. It also distinguishes the filesystem case from chat assistants without files. It does not explicitly say whether the tool returns a script/instructions or performs the conversion itself, which slightly blurs the tool's own action versus agent workflow.

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

Usage Guidelines5/5

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

It clearly names the correct audience: agents with a local filesystem, and explicitly says chat assistants without files should skip it and pass the image directly to upload_asset. The ordering relative to upload_asset is stated up front, leaving little ambiguity about when to use this tool versus the alternative.

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

All Pageree toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources