Skip to main content
Glama
Sign In

GetBotRank Free AI Search Tools

by io.github.lazycipher
OverviewDiscussionsAdmin

AI Citability Analyzer

score_citability

Score each passage of a page for how easily AI answer engines can quote it. Deterministic heuristics, no LLM.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that scoring is 'deterministic heuristics, no LLM', which implies reproducibility and speed, but says nothing about permissions, rate limits, cost, or what a returned score looks like.

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?

Two short sentences with zero waste, and the core purpose is front-loaded ahead of the implementation note. Nothing is restated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool this is nearly complete, but with no output schema the description should sketch the return shape (per-passage scores, scale, granularity). As written, an agent knows what it does but not what it gets back.

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% for the single 'url' parameter, exceeding the baseline, so semantics are already documented. The description adds no further detail such as whether redirects are followed or whether sitemap/canonical variants matter, which is acceptable but not additive.

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?

States a specific verb ('Score') and resource ('each passage of a page') plus the target metric ('how easily AI answer engines can quote it'). This is clearly distinct from siblings like check_entity or validate_schema, though it never names a sibling to contrast against.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative among the 15 siblings. An agent must infer that this is a content-evaluation step, presumably after fetching or generating a page.

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