Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

variety_author

Read-only

Fetch a Variety author's public profile, social links, and one page of recent articles. Use variety_article for one story or variety_headlines and variety_news for current coverage.

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": "variety_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical variety.com/author/<slug> URL, optionally with a /page/<n>/ segment; alternative to slug
pageNo1-based page number; overrides any page number in url
slugNoAuthor slug, e.g. ellise-shafer

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. Changed3 schema fields changed
    • addedInput schema / properties / page / description
      Added value: +"1-based page number; overrides any page number in url"
    • addedInput schema / properties / slug / description
      Added value: +"Author slug, e.g. ellise-shafer"
    • addedInput schema / properties / url / description
      Added value: +"Canonical variety.com/author/<slug> URL, optionally with a /page/<n>/ segment; alternative to slug"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true). The description adds genuine behavioral context beyond them: that only one page of articles is returned and that the payload includes profile and social links. It does not mention rate limits or what happens with a bad slug, so it stops short of a 5.

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 waste. The capability statement is front-loaded and the disambiguation follows immediately, which is the right ordering for a routing decision.

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?

With an output schema present, the description need not describe return values, and it still summarizes them. Annotations cover safety, the schema covers all three parameters, and the sibling routing is explicit — nothing an agent needs to invoke this correctly is missing.

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 schema itself documents the url/slug alternatives and the page-overrides-url precedence rule, so the description adds nothing parameter-specific. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Fetch') and a precisely bounded resource: an author's 'public profile, social links, and one page of recent articles'. This is clearly distinguishable from the sibling article/headlines/news tools, and an agent can tell what it will get 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 routes the agent: 'variety_article for one story' and 'variety_headlines and variety_news for current coverage'. The conditions selecting the alternatives are named, though the description never states when variety_author itself is the wrong choice (e.g., searching by name rather than slug).

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