get_productGet 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.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Product slug from the /p/<slug> URL |
| Name | Required | Description | Default |
|---|---|---|---|
| product | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / product / properties / dealAdded 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"
+}Output schema / properties / product / properties / makerAdded 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"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds genuinely non-obvious context about the returned data's provenance, notably that the tool list is probed from the endpoint rather than maker-supplied tags, plus the 'when available' caveat on the verification timestamp. It stops short of describing failure behavior for an unknown or dead slug.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the operation and scope, followed by a tight enumeration of return fields. Every clause carries information; nothing is redundant or padding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so field structure need not be re-explained, yet the description still usefully clarifies what the probed tool list means semantically. For a one-parameter read tool this is nearly complete; only the not-found/dead-endpoint behavior is left unstated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single slug parameter already documents its format ('Product slug from the /p/<slug> URL'). The description only restates that lookup is by slug, adding no syntax or resolution detail beyond the schema, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Get), resource (FastDrop product), and cardinality/scope (one, by slug, live). The singular 'one ... product by its slug' cleanly separates it from sibling list/search tools like search_products and compare_products without needing to name them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The slug-based framing implies the precondition (you must already have a slug), which is useful, but there is no explicit statement of when to prefer this over search_products, compare_products, or find_alternatives, and no when-not guidance. Usage is inferable rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.