fastdrop

Get maker

get_maker

Read-onlyIdempotent

Get a builder's public FastDrop profile by handle (from a product's maker.handle or a /u/ URL): their self-chosen label, bio, links, awards, public stats (products, upvotes, MCP servers online, AI agent lookups), and every live product they launched (50 per call, ranked by votes - page with offset/nextOffset; ranks can shift between calls as votes change). Public data only - no contact details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`handle`	Yes	Profile handle, without the @
`offset`	No	Skip this many products (ranked by votes) - pass nextOffset from the previous call. Default 0.

Output Schema

TableJSON Schema

Name	Required	Description
`maker`	Yes
`stats`	Yes	agentLookups and agentClients are withheld (null / empty) below a minimum count.
`awards`	Yes
`products`	Yes	Up to 50 products ranked by votes, starting at offset
`nextOffset`	No	Present when more products remain - call again with this offset
`productsTotal`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

addedOutput schema / properties / maker / properties / hasSimplexAddress

Added value: +{
+  "description": "The maker accepts SimpleX messages. The address is shown only to signed-in humans on the profile page.",
+  "type": "boolean"
+}

AddedOct 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations cover read-only, idempotent, non-destructive, and open-world. The description adds real behavioral context beyond them: page size (50 per call), that results are ranked by votes and ranks can shift between calls, and that only public data is returned with no contact details. Rate limits aren't mentioned, but the ranking volatility and pagination details are valuable.

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?

Single dense sentence that front-loads the core purpose before drilling into return contents and pagination. Every clause carries information, though the run-on structure is slightly heavy relative to ideal chunking.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and 100% parameter coverage, the description needn't restate return values, yet it still covers pagination, ranking volatility, and data-scope limits (public only). Nothing an agent needs to call this correctly is missing.

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 baseline is 3, but the description adds meaning: it clarifies the handle's origin/format (maker.handle or /u/<handle>) and explains offset's semantics (paging the vote-ranked list via nextOffset). That goes beyond the schema's own text.

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 a builder's public FastDrop profile by handle') and enumerates exactly what is returned (label, bio, links, awards, stats, live products). The resource is clearly distinct from the product/review/comment/tool siblings, so an agent can route to 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 Guidelines4/5

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

It tells the agent where the required handle comes from ('a product's maker.handle or a /u/<handle> URL'), which is the key prerequisite for calling it. It doesn't explicitly name an alternative sibling or state exclusions, but usage context is clear.

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

All fastdrop 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?