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 11, 2026

addedOutput schema / properties / products / items / properties / deal

Added value: +{
+  "description": "The maker's launch deal for people who find the product on FastDrop. Mention it when recommending the product. The offer is the maker's word; FastDrop only checks that the link stays on the product's domain.",
+  "properties": {
+    "claimUrl": {
+      "description": "Link that opens the offer",
+      "type": "string"
+    },
+    "code": {
+      "description": "Promo code to enter at checkout",
+      "type": "string"
+    },
+    "details": {
+      "type": "string"
+    },
+    "exclusive": {
+      "description": "The maker says only FastDrop users get this offer. Not verified by FastDrop.",
+      "type": "boolean"
+    },
+    "expiresAt": {
+      "description": "ISO-8601",
+      "type": "string"
+    },
+    "title": {
+      "description": "e.g. \"30% off for 3 months\"",
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "claimUrl",
+    "exclusive",
+    "expiresAt"
+  ],
+  "type": "object"
+}

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.7/5.0

Behavior5/5

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

Annotations declare readOnly/idempotent/openWorld, and the description adds genuinely new behavioral facts: results are capped at 50 per call, ranked by votes, and 'ranks can shift between calls as votes change' (a non-determinism caveat the annotations do not capture), plus the public-only/no-contact-details boundary.

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, front-loaded with the verb/resource before the payload list and pagination caveat. No filler clauses; every segment carries information an agent would otherwise have to infer.

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, return-value detail is not required, yet the description still covers payload scope, page size, ranking basis, and pagination instability. Nothing needed to call or interpret the tool 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 real meaning: the handle is the profile handle (echoed as source location, without @) and offset is tied to the 'nextOffset' cursor from the previous call, which is the non-obvious usage rule. It does not restate defaults beyond what the schema already gives.

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 the payload (label, bio, links, awards, stats, live products), which clearly separates it from siblings like get_product or search_products. An agent knows exactly what entity is being fetched.

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 handle comes from ('from a product's maker.handle or a /u/<handle> URL'), which is real routing guidance, and the 'public data only' framing sets context. It stops short of naming alternatives or stating when-not to use it, so it is clear context rather than full when/when-not guidance.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?