Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

space_author

Fetch a Space.com author profile by slug or canonical URL, returning name, job title, bio, image, and recent articles.

Instructions

Get a Space.com author profile. Returns a Space.com author's profile, looked up by slug (for example elizabeth-howell) or canonical url; exactly one is required. The response has the name, job_title, biography, image and the first batch of recent articles on the author page. That page has no URL-based pagination, so no further articles are available.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical space.com/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. elizabeth-howell

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose valuable behavior: the exact response contents (name, job_title, biography, image, first batch of articles) and the important limitation that the page has no URL-based pagination so no further articles are retrievable. This is meaningful context beyond the schema, though it doesn't restate safety/read-only semantics.

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 tight sentences, front-loaded with the purpose, then identity mechanism, then return contents. 'Get a Space.com author profile' and 'Returns a Space.com author's profile' are mildly redundant, but overall it is efficient.

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?

For a read-only lookup with no annotations and no output schema, the description compensates well by naming the returned fields and the pagination dead-end. An agent has enough to call it correctly, though not an explicit statement of when to prefer it over article-fetching siblings.

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 real value beyond the schema: it states that slug and url are mutually alternative and that 'exactly one is required' — a constraint not expressed in the schema (required is empty). It also gives a concrete slug example.

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+resource ('Get a Space.com author profile') and clearly scopes it to author identity, distinguishing it from sibling article/news tools. An agent can tell immediately this returns an author entity, not content.

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?

Provides clear context for use (looking up an author by slug or canonical URL) and states the identity mechanism. It does not, however, explicitly contrast with siblings like space_article or space_news or state any exclusions, so it stops short of full routing guidance.

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