Skip to main content
Glama
Sign In
Drop Beacon

Drop Beacon

by direct-web
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_latest_drops

Read-onlyIdempotent

Find in-stock EDC listings first seen within seven days; filter by category and set a result limit to monitor new product discoveries.

Instructions

Read in-stock listings first seen within seven days. First seen is a discovery date, not a manufacturer release date. Results are a bounded sample, not the entire market.

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / api_key
      Removed value: -{
-  "description": "Optional API key for authenticated access.",
-  "type": "string"
-}
    • removedInput schema / properties / category / description
      Removed value: -"Filter drops by product category (e.g., 'knives', 'flashlights', 'fidgets_haptics')"
    • addedInput schema / properties / category / enum
      Added value: +[
+  "knife",
+  "fidget",
+  "flashlight",
+  "pen",
+  "wallet",
+  "multi_tool",
+  "patch",
+  "other"
+]
    • removedInput schema / properties / limit / description
      Removed value: -"Number of results to return (default: 15, max: 30)"
    • addedInput schema / properties / limit / maximum
      Added value: +25
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
  2. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: 'first seen' is a discovery date rather than a release date, and results are a bounded sample rather than a complete market view. Those caveats materially affect interpretation of the output.

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?

Three short, front-loaded sentences with zero filler; each one carries a distinct piece of information (scope, date semantics, result completeness). Nothing could be cut without losing meaning.

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?

For a read-only two-parameter read tool with annotations covering the safety profile and no output schema, the description supplies the essential scope and data-interpretation caveats. The one gap is parameter meaning, but the small, mostly self-explanatory schema limits the impact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and neither parameter is named or explained. 'Bounded sample' loosely gestures at the limit, and the category enum values are self-describing, but the description does not clarify what limit actually controls (count cap of 25) or how category filters results.

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 ('Read in-stock listings') plus a precise scope ('first seen within seven days'). An agent can distinguish it from check_availability or search_products by the recency window, though no sibling is named explicitly.

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 the seven-day discovery window, and 'bounded sample, not the entire market' hints that a broader search (e.g. search_products) is needed for full coverage. However, no explicit when-to-use or when-not-to-use guidance or named alternative is given.

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

Deploy Server

Other Tools