Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polygon_headlines

Fetch headlines for a chosen Polygon section by supplying one required slug, returning each story's title, URL, summary, publication time, author, and image.

Instructions

Get Polygon section headlines. Returns the latest Polygon stories for one section. section is required and takes one of 15 slugs, including gaming-news, gaming-reviews, movie-tv-reviews, anime, guides and videos. Each item has its title, URL, summary, publication time, author and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesPolygon RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/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 usefully enumerates the fields returned per item (title, URL, summary, publication time, author, image), but says nothing about ordering, result count, pagination, or how fresh the 'latest' stories are.

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 core action and scope, followed by the parameter requirement and the return shape. No filler, though the partial slug enumeration is slightly redundant with the enum.

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

Completeness3/5

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

With no output schema, the description appropriately describes the item fields, which is genuinely useful. However, it omits result count and pagination behavior, leaving an agent unsure how much data to expect from a single call.

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 lists all 15 slugs, so the schema does the heavy lifting. The description's mention of 'one of 15 slugs, including...' largely repeats the enum, adding only the reminder that section is required, which is also in the schema.

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 Polygon section headlines') and clarifies the scope ('latest Polygon stories for one section'). It does not distinguish itself from the nearby siblings polygon_news and polygon_sections, which an agent would need to disambiguate.

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 only implied: the tool returns the latest stories for a given section, so an agent can infer when to call it. There is no explicit when-not guidance and no reference to alternatives like polygon_news or polygon_article.

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