Skip to main content
Glama
Sign In

GetBotRank Free AI Search Tools

by io.github.lazycipher
OverviewDiscussionsAdmin

JavaScript Rendering Checker

check_rendering

Estimate whether a page's content exists in the raw HTML before JavaScript runs (heuristic, no headless browser). Most AI crawlers do not execute JavaScript.

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": {
      "url": "<url>"
    },
    "name": "check_rendering"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL, for example https://example.com/page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose two important traits: the result is heuristic and no headless browser is launched. It does not state the accuracy or failure modes of the heuristic, whether the URL is fetched live (network cost), or what the estimate looks like, so the mutation-free read profile is only partially covered.

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?

Two short sentences, front-loaded with the core estimate and followed by the constraining parenthetical and rationale. Nothing is padding, though the trailing crawler sentence could be folded more tightly.

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 one-parameter read-only checker with no output schema, the description covers the essential risk an agent needs to know: it is a heuristic, not a render. A hint about the returned estimate or whether the page is fetched live would make it fully self-sufficient.

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 description coverage is 100% with a single required string URL, so the schema already does the work; the description adds no format, canonicalization, or redirect-handling detail beyond it. Baseline 3 applies when structured fields fully document the parameters.

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?

A specific verb-plus-resource statement: it estimates whether page content exists in raw HTML before JavaScript execution. That is far more informative than the tautological title, and the parenthetical '(heuristic, no headless browser)' immediately separates it from any true-render sibling. The only gap is that it never names view_as_crawler or another sibling it should be chosen over.

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 sentence 'Most AI crawlers do not execute JavaScript' implicitly tells the agent when this check matters, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer that this is the lightweight complement to a real crawler-view tool.

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

All GetBotRank Free AI Search Tools toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources