Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

phonearena_sections

Lists PhoneArena sections (news, news-month, reviews) accepted by phonearena-headlines. Use these slugs to fetch targeted articles.

Instructions

Get PhoneArena sections. Lists the three PhoneArena listings that phonearena-headlines accepts: news (the last two days of news), news-month (the newest news of the current calendar month) and reviews (the newest reviews, comparisons and hands-on articles of the current year). Each entry has a slug, a display name and a source url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the return shape (slug, name, url) plus the time window and content of each listing. It does not cover permissions or freshness guarantees, but for a static enumeration endpoint this is close to complete.

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?

One short opening sentence, then a single dense enumeration where every clause (slug, date window, article type) adds decision-relevant information. Nothing is repeated or wasted.

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 output schema and a trivial input schema, the description supplies everything the agent needs: the full set of section values, the meaning of each, and the shape of each returned entry.

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, which is the baseline-4 case. The description's value here is that it enumerates the fixed section identifiers, removing ambiguity about accepted values even though there is no schema to document.

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+resource ('Get PhoneArena sections') and then enumerates the exact three slugs it returns. It also names the sibling it feeds (phonearena-headlines), so an agent can distinguish it from phonearena_news/phonearena_headlines without opening a schema.

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?

Explains the practical role: these are the listings phonearena-headlines accepts, which tells the agent when to call this (to discover valid section values). It stops short of an explicit 'call this first' instruction or any when-not guidance, so it is clear context rather than full routing.

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