Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

androidpolice_headlines

Fetch recent Android Police headlines for a required section slug, such as news, phones, or deals, with title, URL, and optional summary.

Instructions

Get Android Police section headlines. Returns recent Android Police headlines for one of 18 sections. section is required and takes a slug such as news, phones, smart-home, ai-machine-learning or deals. Each item has a title and URL, and may also carry a summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesAndroid Police section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.5/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 burden. It usefully discloses the return-item shape (title, URL, and optional summary/author/time/image), which is valuable since there is no output schema. However, it omits pagination, result limits, rate behavior, and whether it is strictly read-only.

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 tight sentences, front-loaded with the purpose and then the parameter and return details. The only mild redundancy is listing example slugs on top of the schema enum, but overall it is efficient and well ordered.

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 single-parameter headline tool with no output schema and no annotations, the description covers what it does, the required parameter, and the item shape. It is largely complete, with only pagination/limit behavior left implicit.

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% and the enum already enumerates all 18 slugs, so the schema does the heavy lifting. The description's example slugs ('news', 'phones', 'smart-home', 'ai-machine-learning', 'deals') restate the enum without adding format or constraint detail, so baseline 3 applies.

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 and resource ('Get Android Police section headlines') and clarifies it returns recent headlines for one of 18 sections. An agent can tell what it does, though it never names or distinguishes itself from close siblings like androidpolice_news or androidpolice_sections.

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 by the description and the required `section` parameter, but there is no explicit statement of when to use this tool versus androidpolice_news, androidpolice_sections, or androidpolice_article. The slug examples aid invocation more than tool selection.

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