Full-fidelity screenshot of any public web page, captured by a real Chrome browser. Viewport or full-page, configurable width. Returns a base64 PNG. JSON response. [Paid: $0.015 USDC per call via x402 on Base; the calling client pays automatically.]
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public page URL | |
| full | No | 1 for full-page, else viewport | |
| width | No | Viewport width 320-2000, default 1280 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses use of real Chrome browser, base64 PNG return, JSON response, and pricing model. Does not detail rate limits or error handling, but adequate for a screenshot tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences plus a pricing note in brackets. Every sentence adds value, front-loaded with core purpose. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 3 simple parameters, no output schema, and no annotations, description covers the main behavior, options, and pricing. Lacks details on return format structure, but sufficient for a straightforward tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and description adds minimal semantics beyond schema: 'configurable width' matches schema detail. Does not introduce new parameter information, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Full-fidelity screenshot of any public web page' with specific verb and resource. It distinguishes from sibling tools (none offer screenshots) and adds detail on viewport/full-page and configurable width.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description implies usage for public web pages only and mentions payment cost, but lacks explicit alternatives or when-not-to-use guidance. However, context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each of the 30 tools has a highly specific, non-overlapping purpose, from brand visibility to chemical safety to YouTube transcripts. Descriptions are detailed and clearly differentiate each tool's function, eliminating ambiguity.
All tool names use lowercase with hyphens, creating a consistent visual pattern. However, the structure varies: some are noun-verb (email-validate, pdf-extract), others noun-noun (brand-visibility, chem-compat). This minor inconsistency prevents a perfect score.
With 30 tools, the server offers a very broad surface. While each tool earns its place as a distinct utility, the high count may overwhelm agents and dilute focus. It is borderline heavy for a single server, hence a score of 3.
The tool set covers a wide range of domains: business, chemicals, crypto, domain, email, finance, holidays, trade, jobs, legal, mapping, medical, news, packages, electronics, PDF, product, recall, sanctions, screenshots, SEC, tech stack, web archive, web search, YouTube. Yet it lacks some common utilities like weather, translation, or image analysis, leaving notable gaps for a general-purpose utility server.