Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polygon_article

Fetch a Polygon article's structured content by canonical URL, including title, authors, publication details, lead image, body paragraphs, and a paywalled flag; non-article URLs are rejected.

Instructions

Get Polygon article content. Returns a Polygon article by canonical url (https://www.polygon.com/<slug>/): title, description, section, authors, publication and update times, lead image, body paragraphs and a paywalled flag. Section, guide and other non-article URLs, such as /gaming-news/ or /guides/, are rejected as an invalid parameter.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Polygon article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses the returned fields (title, description, section, authors, times, lead image, paragraphs, paywalled flag) and the error behavior for invalid inputs, which is strong for a read-only fetch. It does not cover auth, rate limits, or paywall content access semantics, keeping it from a 5.

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?

Front-loads the core action ('Get Polygon article content'), then efficiently lists return values and input constraints in two tight sentences. No filler, every clause adds useful information.

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?

For a simple single-article fetch with no output schema, the description explains both the returned data shape and the input restrictions. An agent has everything needed to call it correctly and interpret the response.

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

Parameters5/5

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

Schema description coverage is already 100%, but the description adds substantial meaning: it specifies the exact URL pattern (`https://www.polygon.com/<slug>/`) and gives explicit examples of invalid URLs (`/gaming-news/`, `/guides/`). This goes well beyond the schema's 'Canonical Polygon article URL'.

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 Polygon article content' and 'Returns a Polygon article by canonical url'. This clearly identifies it as a single-article detail lookup, distinguishing it from sibling list tools like polygon_headlines and polygon_news without needing to name them.

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?

Provides clear context on what URL to pass (canonical article URL) and explicitly states that section, guide, and other non-article URLs are rejected. It does not name alternative tools for listing articles, but the valid/invalid input conditions are enough to guide correct use.

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