Skip to main content
Glama
User0856

snaprender-mcp

by User0856
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

check_screenshot_cache

Read-only

Check if a screenshot is already cached without capturing a new one or using your quota. Use the same parameters as take_screenshot to match the cache key.

Instructions

Check if a screenshot is already cached without capturing a new one. Does not count against your quota. Pass the same parameters you would use for take_screenshot so the cache key matches correctly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to check
widthNoViewport width (default: 1280)
deviceNoDevice preset
formatNoOutput format (default: png)
heightNoViewport height (default: 800)
qualityNoImage quality (default: 90)
block_adsNoBlock ads (default: true)
dark_modeNoDark mode (default: false)
full_pageNoFull page capture (default: false)
click_selectorNoCSS selector to click
hide_selectorsNoCSS selectors to hide

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.5.6
    • addedInput schema / properties / block_ads
      Added value: +{
+  "description": "Block ads (default: true)",
+  "type": "boolean"
+}
    • addedInput schema / properties / click_selector
      Added value: +{
+  "description": "CSS selector to click",
+  "type": "string"
+}
    • addedInput schema / properties / dark_mode
      Added value: +{
+  "description": "Dark mode (default: false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / device
      Added value: +{
+  "description": "Device preset",
+  "type": "string"
+}
    • addedInput schema / properties / full_page
      Added value: +{
+  "description": "Full page capture (default: false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / height
      Added value: +{
+  "description": "Viewport height (default: 800)",
+  "type": "integer"
+}
    • addedInput schema / properties / hide_selectors
      Added value: +{
+  "description": "CSS selectors to hide",
+  "type": "string"
+}
    • addedInput schema / properties / quality
      Added value: +{
+  "description": "Image quality (default: 90)",
+  "type": "integer"
+}
    • addedInput schema / properties / width
      Added value: +{
+  "description": "Viewport width (default: 1280)",
+  "type": "integer"
+}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds meaningful behavioral context beyond annotations: it does not capture a new screenshot and does not count against the quota. These quota and side-effect details are not in the annotations. It doesn't mention return value structure (e.g., boolean vs. metadata), but that's minor given the tool's simplicity.

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?

Three sentences, each carrying weight: purpose, quota exemption, and parameter matching. Front-loaded with the core action and no waste.

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?

With no output schema, the description could mention what is returned (e.g., a boolean or timestamp). However, for a cache-check tool, the purpose, side effects, and key-matching instruction are likely sufficient for an agent to call it correctly. A minor gap in return value description.

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%, so the schema already documents all 11 parameters with descriptions and defaults. The description adds the important constraint that parameters must match those used for take_screenshot for the cache key to align, which is useful context not in the schema. Baseline 3 is appropriate.

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?

States a specific verb ('Check') and resource ('screenshot cache') and explicitly distinguishes from the capture action ('without capturing a new one'). An agent can differentiate this from take_screenshot immediately.

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?

Gives clear context: use it to check cache status before taking a screenshot, and critically instructs to pass the same parameters as take_screenshot so the cache key matches. This is actionable advice for correct invocation, though it doesn't explicitly state when not to use it.

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