Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

screenshot

[object Object]

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": {
      "Screenshot - PNG of any public URL": "<Screenshot - PNG of any public URL>"
    },
    "name": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
Screenshot - PNG of any public URLYesParameter: Screenshot - PNG of any public URL
screenshot,screenshot url,capture webpage,render page,website image,png of pageNoParameter: screenshot,screenshot url,capture webpage,render page,website image,png of page
Rendered screenshot of any public web page as a PNG, width/height up to 2048, optional render delay. For agents that cannot run a browser. Add format=json to get the image URL and metadata instead of the binary.NoParameter: Rendered screenshot of any public web page as a PNG, width/height up to 2048, optional render delay. For agents that cannot run a browser. Add format=json to get the image URL and metadata instead of the binary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

D1.2/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about rate limits, page-load behavior, binary vs JSON responses, or failure modes. The string "[object Object]" provides zero behavioral context for an unannotated tool.

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

Conciseness1/5

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

The description is a single serialization error with no front-loaded statement of purpose. Brevity here reflects a broken tool definition rather than disciplined writing.

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?

For an unannotated three-parameter tool with no output schema, the description should explain what is captured, output format options, and return shape. None of that is present, so the definition is not callable with confidence.

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?

Schema description coverage is nominally 100%, which would normally set a baseline of 3, but the schema itself is malformed — parameter names are full sentences and the descriptions merely restate them, so no real semantics are conveyed anywhere. The description adds nothing to compensate for what is effectively unusable parameter documentation.

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 is the literal string "[object Object]", an unrendered serialization artifact that conveys no verb, resource, or scope. Any sense of purpose comes only from the tool name 'screenshot', which the description does nothing to confirm or differentiate from siblings such as 'ocr', 'scrape', or 'meta_scrape'.

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?

There is no when-to-use guidance, no alternatives named, and no exclusions. An agent has no basis for choosing this over 'scrape', 'crawl', 'ocr', or 'analyze_url'.

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

All GadgetHumans API Hub 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