Skip to main content
Glama

EarlyLore

earlylore_inspect_creator

Read-onlyIdempotent

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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered and the description's added burden is lower. It contributes the dual-mode behavior (single creator vs leaderboard) but says nothing about data freshness, pagination, or the shape/cost of the monthly revenue series for a read-only open-world tool.

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?

A single dense sentence, front-loaded with the verb and the value proposition, with the mode-switching clause placed last. Every clause maps to real functionality; the one weakness is the long comma-separated field inventory, which is slightly harder to scan than a short structured list.

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 five optional parameters, no output schema, and clear annotations, the description covers the two operating modes and the metrics available, which is enough for an agent to decide and call correctly. Missing only return-format and volume expectations, which are minor given the rich schema coverage.

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 description coverage is 100%, so every parameter including the list enum, limit defaults/max, and the creatorSlug omit-behavior is already documented in the schema. The description restates the omit-creatorSlug rule rather than adding new semantics such as slug format or how category interacts with list mode. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 a specific resource ("indie creators and serial makers' product portfolios"), then enumerates the data returned: verified MRR, monthly revenue series, launch cadence, niche distribution, recent activity. That is concrete enough to distinguish it from product-level siblings like earlylore_inspect_product, but it never names a sibling or states the distinction explicitly.

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?

It gives one actionable routing rule — "omit creatorSlug to browse creator leaderboards" — which separates detail mode from list mode. Beyond that there is no guidance on when to prefer this over earlylore_search_products or earlylore_compare_products, and no prerequisites or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.