Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sloanreview_topic

Read-only

The newest public MIT Sloan Management Review article cards on one topic archive; use sloanreview_categories for the complete topic slug set.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "sloanreview_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesSloan Review topic slug returned by sloanreview-categories. Documented values: ai-machine-learning, analytics-business-intelligence, automation, boards-corporate-governance, business-models-strategy, climate-change, collaboration, corporate-social-responsibility-sustainability, crisis-management, culture, customers, data-ai-machine-learning, data-culture, developing-strategy, digital-marketing, disruption, diversity-inclusion, equality, ethics, executing-strategy, financial-management-risk, global-strategy, innovation-3, innovation-strategy, it-governance-leadership, leadership, leadership-skills, leading-change, managing-technology, managing-your-career, marketing, marketing-strategy, new-product-development, operations, organizational-behavior, organizational-structure, organizational-transformation, performance-management, platforms-ecosystems, project-management, quality-service, remote-work, security-privacy, skills-learning, social-media, social-responsibility, strategy, supply-chains-logistics, sustainability-social-responsibility, talent-management, technology-implementation, technology-innovation-strategy, work-life-balance, workplace-teams-culture.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / topic / description
      Added value: +"Sloan Review topic slug returned by sloanreview-categories. Documented values: ai-machine-learning, analytics-business-intelligence, automation, boards-corporate-governance, business-models-strategy, climate-change, collaboration, corporate-social-responsibility-sustainability, crisis-management, culture, customers, data-ai-machine-learning, data-culture, developing-strategy, digital-marketing, disruption, diversity-inclusion, equality, ethics, executing-strategy, financial-management-risk, global-strategy, innovation-3, innovation-strategy, it-governance-leadership, leadership, leadership-skills, leading-change, managing-technology, managing-your-career, marketing, marketing-strategy, new-product-development, operations, organizational-behavior, organizational-structure, organizational-transformation, performance-management, platforms-ecosystems, project-management, quality-service, remote-work, security-privacy, skills-learning, social-media, social-responsibility, strategy, supply-chains-logistics, sustainability-social-responsibility, talent-management, technology-implementation, technology-innovation-strategy, work-life-balance, workplace-teams-culture."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds modest behavioral context: the results are the 'newest' cards (recency ordering) and only 'public' articles are returned. It says nothing about result count, pagination, or whether non-public/paywalled articles are excluded.

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 with no filler, front-loading what is returned and then the prerequisite alternative. Every clause 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?

With an output schema present, return-value detail is unnecessary, and the single required parameter is fully documented in the schema. The definition covers the recency/public scope and the slug prerequisite; the only gap is not clarifying how it relates to sloanreview_articles and sloanreview_headlines.

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 coverage is 100% and the topic parameter already enumerates every valid slug in the schema. The description only echoes the field concept ('one topic') and redirects to sloanreview_categories, so it adds little beyond the structured data — the baseline 3 is appropriate.

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?

The description names the resource (MIT Sloan Management Review article cards) and the scope (a single topic archive), and it explicitly points at sloanreview_categories for the slug set, which separates it from that sibling. It does not, however, distinguish itself from sloanreview_articles or sloanreview_headlines, which likely also return article content.

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 gives an explicit when-to-use pointer by naming sloanreview_categories as the source of valid topic slugs, which is the key prerequisite for calling this tool. It stops short of stating exclusions or contrasting with the other article-listing siblings.

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

All Crawlora MCP toolsInspect
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