Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

physorg_news

Fetch Phys.org top stories from its public all-stories RSS feed, returning current titles and publisher teasers for science news monitoring without manual browsing.

Instructions

Get Phys.org top stories. Returns current stories from Phys.org's public all-stories RSS feed. Summaries are publisher-provided teasers. Use physorg-sections to discover the topic and editorial RSS feeds accepted by physorg-headlines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.1/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 burden and does useful work: it names the underlying source (public all-stories RSS feed) and warns that summaries are publisher-provided teasers rather than full text. It omits pagination/rate-limit behavior, but for a public read-only feed that gap is minor.

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?

Three short sentences, front-loaded with the primary purpose before the source detail and the sibling routing hint. Every sentence contributes distinct information with no filler.

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 parameterless, read-only RSS tool with no output schema or annotations, the description covers purpose, data source, content quality (teasers), and related tools. Only the absence of any mention of result volume or refresh cadence keeps it from being fully complete.

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 of 4 applies. The description correctly implies a no-argument call by describing a fixed feed, and there is no schema surface that needs further explanation.

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 Phys.org top stories') and pins the scope to the public all-stories RSS feed, which implicitly separates it from the topic/editorial feeds handled by physorg-headlines. It names sibling tools but doesn't draw an explicit contrast between 'top stories' and 'headlines', leaving a small ambiguity.

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?

Gives clear routing guidance: use physorg-sections to discover topic and editorial feeds, which are then consumed by physorg-headlines. This orients the agent toward the right sibling, though it never states when this tool should NOT be used or how it relates to physorg-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