Skip to main content
Glama

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.

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

Input Schema

NameRequiredDescriptionDefault
handleYesProfile handle, without the @
offsetNoSkip this many products (ranked by votes) - pass nextOffset from the previous call. Default 0.

Output Schema

NameRequiredDescriptionDefault
makerYes
statsYesagentLookups and agentClients are withheld (null / empty) below a minimum count.
awardsYes
productsYesUp to 50 products ranked by votes, starting at offset
nextOffsetNoPresent when more products remain - call again with this offset
productsTotalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / products / items / properties / domainVerified
      Added value: +{
      +  "description": "True when the maker proved they control the product URL domain by publishing a _fastdrop TXT record (the DOMAIN VERIFIED badge on the website). Independent of mcpVerified.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • 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"
      +}
  3. Changed1 schema field changed
    • 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"
      +}
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, non-destructive, idempotent, and closed-world, so the description correctly spends its budget on behavior the annotations can't convey: 50 products per call, vote-ranked ordering that can shift between calls, nextOffset-based paging, and the public-data-only scope with no contact details. That ranking volatility caveat is genuinely useful and not derivable from the hints.

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?

Front-loaded with the verb and resource, and every clause carries information (contents, handle source, paging, ranking volatility, privacy scope). It is a single very dense sentence with nested parentheticals, which slightly taxes parsing but wastes no words.

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?

For a two-parameter read tool with an output schema, annotations, and full schema coverage, the description covers everything an agent needs: what it returns, how to obtain the handle, how paging works, and that results may reorder. No material gap remains.

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 the baseline is 3, but the description adds meaning beyond it by disclosing the page size (50 per call), the vote-based ranking that makes offset paging unstable, and the intent that offset should be fed from a previous nextOffset. Handle formatting (without @) is left to the schema, which already states it.

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+resource ('Get a builder's public FastDrop profile by handle') and enumerates exactly what the profile contains (label, bio, links, awards, stats, live products). This is clearly distinguishable from siblings like get_product or search_products, which operate on products rather than makers.

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?

Tells the agent where the handle comes from ('from a product's maker.handle or a /u/<handle> URL'), which is the key precondition for invoking it. It does not explicitly say when to prefer a sibling instead, but for a lookup-by-identifier tool the trigger condition is effectively given.

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.

Resources