Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

variety_headlines

Read-only

Fetch current Variety story cards for one section slug from variety_sections. Use variety_news for the general feed or variety_article for one story.

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": {
      "section": "<section>"
    },
    "name": "variety_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesVariety vertical slug. Documented values: artisans, awards, biz, data, digital, dirt, film, gaming, global, legit, music, politics, scene, shopping, sports, streaming, theater, tune-in, tv, video, vintage, vip, vivant, voices.

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 / section / description
      Added value: +"Variety vertical slug. Documented values: artisans, awards, biz, data, digital, dirt, film, gaming, global, legit, music, politics, scene, shopping, sports, streaming, theater, tune-in, tv, video, vintage, vip, vivant, voices."
  2. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that results are section-scoped and 'current', but says nothing about pagination, result volume, or ordering. Matching the calibration baseline: adequate added context, not rich behavioral disclosure.

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, zero filler, with the tool's own scope front-loaded ahead of the alternative-tool routing. Every clause 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?

A single-parameter, read-only feed tool with a documented slug list, an output schema (so return values need no prose), and clean sibling routing. Nothing an agent needs to call 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?

Schema coverage is 100% and already lists every valid slug, so the schema carries most of the load. The description still adds provenance by pointing to variety_sections as the source of valid slug values, which is a genuine hint beyond the enum listing.

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 ('Fetch current Variety story cards') plus the scoping unit ('one section slug'), and names the sibling tools it is not (variety_news, variety_article). An agent can distinguish it from all three Variety siblings without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: variety_news for the general feed, variety_article for a single story, and this tool for a per-section card feed sourced from variety_sections. The when-to-use condition is stated, not implied.

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