Skip to main content
Glama

Get product

get_product
Read-onlyIdempotent

Get one live FastDrop product by its slug. Returns the MCP URL if set, mcpVerified, last-verified timestamp when available, and the probed tool list (name + description) read from the endpoint - not maker-supplied tags.

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": {
      "slug": "<slug>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug from the /p/<slug> URL

Output Schema

NameRequiredDescriptionDefault
productYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / product / 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 / product / 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 / product / properties / maker
      Added value: +{
      +  "description": "Who built the product. label is their own description of themselves (e.g. \"Indie hacker\"), \"Builder\" when unset. handle and profile are present once they have a public FastDrop profile.",
      +  "properties": {
      +    "handle": {
      +      "type": "string"
      +    },
      +    "label": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "profile": {
      +      "description": "Public profile URL",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "label"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description's added value is the provenance note that the tool list is 'probed ... read from the endpoint - not maker-supplied tags' and the conditional 'when available' fields, but it says nothing about behavior on a missing, unpublished, or unreachable product.

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?

Two tight sentences, front-loaded with the action and resource, then the returned fields and provenance caveat. No sentence is filler and the important qualifier ('not maker-supplied tags') is placed where it lands.

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 an output schema present, the description does not need to enumerate return values, and it already flags conditional fields and data provenance. The main gap is the absence of not-found / not-live behavior for a lookup by unique slug.

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?

There is a single parameter with 100% schema coverage, including a description pointing at the /p/<slug> URL origin. The description restates 'by its slug' but adds no format, casing, or resolution rules beyond the schema, so the 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?

States a specific verb and resource ('Get one live FastDrop product by its slug') and scopes it to live products, which distinguishes it from list/search siblings. It does not explicitly name an alternative such as search_products or get_maker, so it stops short of a 5.

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?

Usage is implied by naming the required identifier ('by its slug'), so an agent knows it needs a slug from a /p/<slug> URL. There is no explicit when-to-use versus when-not-to-use guidance relative to search_products, find_alternatives, or get_maker.

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