Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

physorg_headlines

Fetch current Phys.org section headlines from verified RSS feeds, including topics, breaking, and editorials. Returns clean JSON for aggregating science news by section.

Instructions

Get Phys.org section headlines. Returns current stories from one verified public Phys.org RSS feed. The accepted values are the seven Topics menu feeds plus the Breaking and Editorials feeds. Search and tag feeds are excluded because their paths are disallowed in robots.txt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesPhys.org RSS feed slug from physorg-sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses that results come from a verified public RSS feed and that some paths are disallowed by robots.txt, implying a read-only, allow-listed operation, but it says nothing about result freshness, item counts, auth, or rate limits.

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 sentences, no padding, and the core purpose is front-loaded. The robots.txt sentence is slightly tangential but earns its place by justifying the restricted enum.

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 one-parameter list tool with no output schema, the description covers source, scope, and the allowed value set adequately. Only minor gaps remain around return shape and freshness, which are not an agent's main selection concern here.

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?

Schema coverage is 100%, so the enum is already documented, but the description adds genuine value by explaining the enum's composition — seven Topics feeds plus Breaking and Editorials — and the rationale for excluded feed types.

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 Phys.org section headlines') and clarifies the source is a single verified public RSS feed. This clearly separates it from physorg_article, physorg_news, and physorg_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?

The description explains which feeds are valid and why others (search/tag feeds) are excluded due to robots.txt, which is useful scoping. However, it never states when to choose this tool over the sibling physorg_news or physorg_sections tools.

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