Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

androidpolice_article

Fetch structured Android Police article data by canonical URL, including title, authors, section, times, image, and readable body paragraphs.

Instructions

Get Android Police article content. Returns an Android Police article by url, a canonical address with a flat, single-slug path. The response has the title, authors, section, description, publication and update times, image and the readable body paragraphs.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Android Police article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/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 helpfully enumerates the returned fields (title, authors, section, publication/update times, image, paragraphs), implying a read-only operation, but says nothing about permissions, rate limits, or failure behavior for a bad URL.

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?

Three sentences, front-loaded with the core action, then the input constraint, then the return shape. No filler; the return-field list is long but justified since no output schema exists.

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?

Given a single required parameter, no output schema, and no annotations, the description covers input format and the returned fields well. It would be fully complete with a note on error handling or the read-only nature.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and documents the single url parameter. The description adds genuine meaning beyond the schema by specifying the path must be a canonical, flat, single-slug address, which constrains the accepted format.

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 (Get) and resource (Android Police article content), and clarifies it returns an article by canonical URL. It is clearly the article-level tool versus androidpolice_headlines/news, though it does not explicitly name those siblings.

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: the tool requires a canonical article URL and returns the body. There is no explicit when-to-use or when-not-to-use guidance, nor any pointer to the headlines/news/sections siblings as alternatives for listing.

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