Skip to main content
Glama
Sign In

EarlyLore

by io.github.jiangqizheng
OverviewDiscussionsAdmin

earlylore_inspect_creator

Inspect indie creators and serial makers’ product portfolios, total verified MRR, monthly revenue series, launch cadence (median gap days), niche distribution, and recent activity; omit creatorSlug to browse creator leaderboards.

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

Input Schema

NameRequiredDescriptionDefault
listNoCreator leaderboard view: launching (recent launches), revenue (verified revenue), serial (multi-product makers)
limitNoNumber of creators returned (default 15, max 40)
queryNoSearch creators by name or X handle
categoryNoFilter creators by niche category slug
creatorSlugNoCreator slug or @handle (omit to browse creator lists by list and query)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are present, so the description carries the full behavioral burden. It discloses the data dimensions returned and the leaderboard browsing behavior, but does not cover auth needs, data freshness, or whether the revenue figures are verified or limited to a subset.

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?

A single dense sentence with a semicolon cleanly front-loads the purpose and appends the mode-selection rule; there is no filler. It could have been split for readability, but nothing is wasted.

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?

With no output schema and no annotations, the description must convey enough for an agent to call it correctly. It names the returned dimensions and browsing mode, though it stops short of response-shape details such as pagination metadata or data freshness.

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 baseline is 3; the description adds only the creatorSlug omission behavior, which is already documented in the schema. It does not add syntax examples for query, category, or the enum values beyond what the schema states.

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?

The description opens with a specific verb ('Inspect') and resource ('indie creators and serial makers'), then enumerates the exact portfolio, revenue, cadence, niche and activity data the tool surfaces. That is enough to distinguish it from sibling product-inspection and comparison tools.

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?

It explicitly defines the two main modes: supply creatorSlug to inspect a creator, or omit it to browse leaderboards. It does not compare itself with named alternatives or state when not to use it, so it is clear but not exhaustive.

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

All EarlyLore 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