Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sloanreview_topic

Fetch article cards from a public MIT Sloan Management Review topic page using a valid topic slug; use sloanreview-categories to get accepted slugs.

Instructions

Get an MIT Sloan Management Review topic archive. Returns article cards from one public Sloan Review topic page. Use sloanreview-categories for the complete accepted slug set; this includes the primary navigation topics and the site's child topic pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesSloan Review topic slug returned by sloanreview-categories

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?

No annotations are present, so the description carries the transparency burden. It discloses that the tool is public, read-oriented, scoped to one topic page, and returns article cards. Pagination or rate-limit details are absent, but for a simple public fetch the key behavioral facts are provided.

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 tight sentences with no filler: the first states the action and output, the second gives essential slug-sourcing guidance. Every sentence earns its place.

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?

For a single-parameter tool with no output schema, this is complete. It tells the agent what the tool returns, what it operates on, and where to obtain valid parameter values; nothing needed for a successful call 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 schema already covers the topic parameter fully with an enum and a description referencing sloanreview-categories. The description adds extra semantic value by explaining that the accepted slug set includes both primary navigation topics and child topic pages, going beyond the schema's bare pointer.

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?

The description opens with the specific verb 'Get' and names the exact resource ('MIT Sloan Management Review topic archive'), then narrows the behavior to 'article cards from one public Sloan Review topic page'. It also distinguishes itself from sloanreview-categories by directing the agent there for slug sets.

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?

It explicitly tells the agent to use sloanreview-categories for the complete accepted slug set and clarifies that child topic pages are included. It gives clear context for the main alternative it must consult, though it doesn't enumerate exclusions for other sibling tools like sloanreview_articles or sloanreview_headlines.

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