Awesome Indie

Get a maker profile

get_maker

Read-only

A maker profile by username: bio, links, streak, followers and their launched products.

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": {
      "username": "<username>"
    },
    "name": "get_maker"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	The username, without the @

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4/5.0

Behavior3/5

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

The readOnlyHint annotation already covers the safe, non-mutating nature. The description adds useful response-scope context—bio, links, streak, followers, and launched products—but does not disclose behavior around missing usernames, rate limits, or response format.

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?

The description is a single compact sentence with the retrieval key up front and the field list after the colon. Every part is informative and there is no 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?

For a simple read-only lookup, the input key and output contents are both covered, and annotations handle the safety profile. Minor gaps remain around not-found behavior and the exact shape of launched products, but they are not critical for selecting and invoking the tool.

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 input schema fully documents the single parameter and even specifies 'without the @'. The description only repeats 'by username' and adds no additional parameter semantics beyond the schema, so the baseline score 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?

The description clearly identifies the resource (a maker profile), the lookup key (username), and the specific data returned (bio, links, streak, followers, launched products). Despite lacking an explicit verb, the tool name and title supply it, and the resource is distinct from sibling tools like get_product or get_article.

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?

The description implies clear usage context: use this tool when you need a maker profile by username. It does not explicitly name alternatives or exclusions, but the sibling names and the profile-specific field list make routing straightforward.

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

All Awesome Indie tools Inspect

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

Need Help?