Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

foreignaffairs_topic

Get recent items from a Foreign Affairs topic RSS feed by providing a valid topic slug. Invalid topics are rejected before any upstream request, ensuring clean JSON output.

Instructions

Get a Foreign Affairs topic feed. Returns the newest items from one Foreign Affairs topic RSS feed. Discover accepted values with foreignaffairs-topics; unknown topic values are rejected before upstream I/O.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesForeign Affairs topic slug from foreignaffairs-topics

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It does disclose that unknown values are rejected before upstream I/O and that results are newest items, but it omits response shape, pagination, or any rate-limit/auth context. Minimum viable but not rich.

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?

Two sentences with no filler. The core action is front-loaded, and the validation/discovery guidance follows immediately. Every sentence earns its place.

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 feed tool with no output schema and no annotations, the description covers the essential invocation path: what it returns, how to get a valid parameter, and failure behavior. The only minor gap is the hyphenated tool reference 'foreignaffairs-topics' versus the actual sibling name 'foreignaffairs_topics.'

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 already covers the single topic parameter at 100%, so baseline is 3. The description adds value by telling the agent where to find valid values (foreignaffairs-topics) and that invalid values fail early, going beyond the schema's phrasing 'slug from foreignaffairs-topics.'

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?

Description states a specific verb and resource: 'Get a Foreign Affairs topic feed' and clarifies it returns 'the newest items from one Foreign Affairs topic RSS feed.' This clearly differentiates from siblings like foreignaffairs_headlines (general headlines) and foreignaffairs_topics (topic discovery).

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?

Explicitly tells the agent to discover accepted values via foreignaffairs-topics and warns that unknown topics are rejected before upstream I/O. This is strong guidance for when to use the discovery sibling, though it does not explicitly contrast with other feed-like siblings.

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