Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

androidpolice_sections

Lists all 18 feed-backed sections in Android Police’s primary navigation, returning each section’s slug, display name, and feed URL for headlines retrieval.

Instructions

Get Android Police sections. Lists the 18 feed-backed sections in Android Police's primary navigation, from news, phones and tablets to deals, videos and awards. Each entry has a slug, a display name and the feed url, and the slugs are accepted by androidpolice-headlines.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does disclose meaningful behavior: the exact count (18), that they are feed-backed, and the per-entry shape (slug, name, url). It doesn't state read-only/caching behavior explicitly, but 'Get/List' plus the downstream-consumption note conveys the read-only nature adequately.

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 sentences, front-loaded with the core action and the size of the result set, then the field shape, then the downstream hook. Every clause earns its place with no filler.

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?

With no input parameters, no output schema and no annotations, the description supplies everything an agent needs: what it returns, how many, the field names, and where the slugs can be reused. Nothing material is left to inference.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter surface for the description to clarify or obscure. Nothing in the description misrepresents the (empty) input contract.

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 and resource ('Get Android Police sections') and immediately scopes it as 'the 18 feed-backed sections in Android Police's primary navigation'. The enumeration of example slugs and the field list (slug, name, url) make it unmistakable against siblings like androidpolice_headlines or androidpolice_news.

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

Usage Guidelines4/5

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

It explicitly ties the output to a downstream action: 'the slugs are accepted by androidpolice-headlines', which tells an agent why and when to call this before that tool. It does not state when-not to use it or name alternative section-discovery routes, so it stops short of full routing guidance.

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