Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

usmagazine_author

Read-only

Fetch a Us Weekly author's public profile, biography, contact links, and recent articles. Use usmagazine_article for one story or usmagazine_headlines for current headlines.

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": {
      "url": "<url>"
    },
    "name": "usmagazine_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Us Weekly author URL

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 / url / description
      Added value: +"Canonical Us Weekly author URL"
  2. First observed

TDQS

A4/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 and reach profile is covered. The description adds content scope (profile, bio, contact links, recent articles), but says nothing about auth needs, rate limits, or freshness beyond what annotations and the output schema imply. Adequate given the annotations carry the behavioral load.

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 tight sentences with the tool's scope front-loaded and the sibling routing trailing. Zero filler.

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?

An output schema exists, so return values need no explanation, and the single param plus annotations are well covered. For a read-only single-param fetch, the description is nearly complete; only minor gaps like URL canonicalization expectations remain.

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?

The single url parameter has 100% schema description coverage ('Canonical Us Weekly author URL'), so the schema documents it fully. The description adds no format, canonicalization, or lookup guidance beyond the schema, which is the correct baseline 3 when schema coverage is high.

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 resource (Us Weekly author's public profile) and enumerates the returned content: biography, contact links, and recent articles. It also names the sibling tools it is not, so an agent can distinguish it from usmagazine_article and usmagazine_headlines without opening either 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: 'Use usmagazine_article for one story or usmagazine_headlines for current headlines,' giving conditions that select the alternatives. It stops short of stating when-not to use this tool or other siblings like usmagazine_news/sections, but the routing signal 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