Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

theblaze_author

Read-only

Get a Blaze Media contributor's public profile and up to 30 recent stories. Pass exactly one of slug or canonical profile URL; use the /theblaze/sections and /theblaze/headlines tools for section browsing.

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

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical HTTPS theblaze.com/u/<slug> profile URL
slugNoTheBlaze author username

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. Changed2 schema fields changed
    • addedInput schema / properties / slug / description
      Added value: +"TheBlaze author username"
    • addedInput schema / properties / url / description
      Added value: +"Canonical HTTPS theblaze.com/u/<slug> profile URL"
  2. First observed

TDQS

A4.5/5.0
Behavior4/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 genuinely useful behavior beyond that: the profile is public and the story list is capped at 30 items. It doesn't mention auth or pagination, but the 30-item cap is real added context.

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, no waste, with the core purpose front-loaded and the parameter rule and sibling routing following in priority order.

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 simple read tool with a full-coverage schema and an output schema, the description covers purpose, the required input rule, the result-size cap, and sibling disambiguation. 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%, so the baseline is 3, but the description adds the mutual-exclusivity rule ('exactly one of slug or canonical profile URL') which the schema does not encode (additionalProperties false, no oneOf). That is meaningful semantics beyond the schema.

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 (Get) and resource (Blaze Media contributor's public profile plus up to 30 recent stories), and explicitly names the sibling tools (/theblaze/sections and /theblaze/headlines) it should not be confused with. An agent can tell exactly what this returns versus neighboring endpoints.

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?

Gives an explicit invocation constraint ('Pass exactly one of slug or canonical profile URL') and routes section-browsing intent to the section and headlines tools. It stops short of naming when to prefer slug over URL, but the context boundary with siblings is clear.

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