Crawlora MCP

sloanreview_articles

Read-only

A paginated sitemap-backed index of all MIT Sloan Management Review article URLs, for discovery before archive-backed article retrieval.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sloanreview_articles"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	1-based page number (default 1)
`page_size`	No	Items per page, 1-500 (default 100)

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026
- addedInput schema / properties / page / description
```
Added value: +"1-based page number (default 1)"
```
- addedInput schema / properties / page_size / description
```
Added value: +"Items per page, 1-500 (default 100)"
```
First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), yet the description adds real signal: results are paginated, the source is a sitemap, and the index covers all article URLs. That tells the agent this is a complete, possibly non-real-time URL listing rather than a search or full-text endpoint.

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?

A single sentence that front-loads the resource and its nature (paginated, sitemap-backed) before the intended use. Every clause carries information; nothing is redundant.

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?

With an output schema present, return values need no explanation, and both optional parameters are fully documented in the schema. The description adequately covers source and purpose; only the exact handoff to the retrieval sibling is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for both page and page_size, so the schema already explains 1-based numbering, ranges and defaults. The description mentions pagination but adds no format, ordering, or range detail beyond what the schema provides, so baseline 3 applies.

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+resource: a paginated index of MIT Sloan Management Review article URLs. It also distinguishes itself from the singular sloanreview_article by framing itself as the discovery step before retrieval, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for discovery before archive-backed article retrieval' implies the two-step workflow, which is genuine usage context. However, no alternative tool is named and there are no when-not conditions, so the agent must still infer which sibling to call for the retrieval step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?