Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rothys_page

Retrieve a Rothy's static page by handle, returning its title, URL, timestamps, and plain-text content; invalid handles return 404.

Instructions

Get a Rothy's static page. Returns a single Rothy's static page for the given handle: its title, URL, created, published and updated times, and body as plain text in content. A handle that does not exist returns 404. In ssr_embedded mode id is absent, because that source has no numeric id.

Input Schema

NameRequiredDescriptionDefault
handleYesPage handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it enumerates returned fields (title, URL, created/published/updated times, plain-text `content`), discloses 404 for a non-existent handle, and notes `id` is absent in `ssr_embedded` mode. Missing auth/permission context keeps it short of a 5.

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 front-loaded sentences: purpose first, then return shape, then error and edge case. No filler, and each sentence contributes distinct information.

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

Completeness5/5

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

For a single-parameter read with no output schema and no annotations, the description supplies the return field list, the 404 failure mode, and the mode-dependent `id` behavior — everything an agent needs to invoke and interpret it. Nothing material is missing.

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% and the sole parameter `handle` is already documented as 'Page handle'. The description only implies that the handle identifies the page; it adds no format, casing, or lookup syntax beyond the schema, so baseline 3 applies.

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 (Get) and resource (a Rothy's static page) scoped to a single page fetched by `handle`, which cleanly separates it from the plural sibling rothys_pages. An agent can tell it retrieves one page by identifier without opening the schema.

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?

Usage is implied ('Get a Rothy's static page... for the given handle') but there is no explicit when-to-use versus rothys_pages/rothys_collections, and no prerequisites stated. The 404 note is behavioral rather than a routing guideline, so this stays at implied-usage level.

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