Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

arstechnica_author

Retrieve an Ars Technica contributor's profile, byline metadata, biography, and recent articles from a canonical author URL.

Instructions

Get an Ars Technica contributor profile. Returns an Ars Technica contributor's byline metadata (name, job title, headshot, contact email), biography, and recent articles from a canonical author URL. The service does not bypass authentication or access controls.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Ars Technica contributor URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the returned fields and adds a note that the service 'does not bypass authentication or access controls,' which is useful compliance context. It omits rate limits, pagination, and error behavior for an invalid URL, so it is only partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences that are front-loaded with the purpose and return payload. The final authentication/access-control sentence is somewhat boilerplate and does not earn much space, keeping it just below fully tight.

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?

No output schema exists, so the description usefully enumerates the return payload (byline metadata, biography, recent articles). For a simple one-parameter read tool this is close to complete, though it could clarify what a canonical URL looks like or how many recent articles are returned.

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%, so the single 'url' parameter is already fully documented as a 'Canonical Ars Technica contributor URL.' The description restates this constraint but adds no format or example detail beyond the schema, so the baseline of 3 applies.

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 (Get an Ars Technica contributor profile) and enumerates the returned content (byline metadata, biography, recent articles). This clearly distinguishes it from arstechnica_article, arstechnica_headlines, and arstechnica_news, so an agent can select it 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 Guidelines3/5

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

The phrase 'from a canonical author URL' implies that a canonical contributor URL is the required input, which is a form of implied usage guidance. However, it never says when to reach for this tool versus the article/headline/news siblings, nor how to obtain a canonical author URL, so guidance is only implied.

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

Deploy Server

Other Tools