Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

physorg_sections

List Phys.org RSS sections, covering seven topic feeds plus Breaking and Editorials, to find valid slugs for physorg-headlines.

Instructions

List Phys.org RSS sections. Lists the seven topic feeds in Phys.org's Topics menu and its two additional public Breaking and Editorials feeds. Every returned slug is accepted by physorg-headlines. Search and tag feeds are excluded because their paths are disallowed in robots.txt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries full burden, and it does disclose substantive traits: the count and composition of returned feeds and the robots.txt reason for excluding search/tag feeds. It omits auth/rate-limit/return-shape detail, but for a zero-parameter list endpoint this is more context than most peers provide.

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 sentences, front-loaded with the one-line purpose, then scope, then the downstream-contract detail. Every sentence adds a fact an agent would otherwise have to discover by calling the tool.

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 parameters, no output schema, and low complexity, this is complete: the agent knows what it returns, roughly how many, and what to do with each slug. Nothing needed to invoke it correctly is missing.

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 no parameters, so there are no semantics to document; baseline is 4. The description correctly implies the call is parameterless and just enumerates the available section slugs.

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 ("List Phys.org RSS sections") and immediately scopes what those sections are: seven topic feeds plus two Breaking/Editorials feeds. This lets an agent distinguish it from physorg_news, physorg_headlines, and physorg_article without opening any 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?

"Every returned slug is accepted by physorg-headlines" is an explicit routing hint for how the output feeds the next call, and the robots.txt sentence scopes what is excluded. There is no explicit when-not-to-use or named competing alternative, so it falls short of 5.

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