Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sloanreview_headlines

Retrieve MIT Sloan Management Review homepage headlines, including editor picks and tiled article cards, with titles, URLs, topics, authors, and publication dates.

Instructions

Get MIT Sloan Management Review headlines. Returns the article cards on the MIT Sloan Management Review homepage, including editor picks and tiled feeds, with no parameters. Each item has a title and url and, when present, topic, authors and published_at. It covers the homepage only; the articles endpoint finds URLs beyond it.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 reasonably well: it discloses that there are no parameters, what the response contains (homepage cards including editor picks and tiled feeds), the field shape of each item, and the coverage boundary. It omits any note on pagination, caching, or freshness, which keeps it out of the top band.

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 tight sentences, front-loaded with purpose then scope, then return shape and boundary. Every sentence carries distinct information with no repetition of the schema or filler.

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?

There is no output schema, and the description compensates by listing the returned fields (title, url, and conditional topic/authors/published_at) along with the coverage boundary. For a no-parameter homepage-scraper, nothing an agent needs 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 zero parameters, so the baseline is 4. The description confirms 'with no parameters', which correctly sets expectations that no input is required, adding nothing misleading.

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 MIT Sloan Management Review headlines') and enumerates the exact content scope (homepage article cards, editor picks, tiled feeds). It also distinguishes itself from the sibling article/article-listing tools by naming the boundary. An agent can identify the tool without opening the 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?

Explicitly states the scope limit ('covers the homepage only') and routes the agent to the alternative ('the articles endpoint finds URLs beyond it'), which is a genuine when-not rule. It does not name the exact sibling tool (sloanreview_articles) or spell out the positive use case, so it stops just short of fully explicit routing.

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