Skip to main content
Glama

Dropyour

by io.dropyour

List a drop's versions

dropyour_list_versions
Read-only

List the published versions of a GRADUATED app (level 4), newest first, with the one currently served. Levels 1-3 have no history at all — replace overwrites the blob under the same key — so they return graduated=false and an empty list. If the app's backend cannot be reached you get degraded=true: that means 'unknown', NOT 'nothing published'. With an account token, owned drops need no managementToken.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dropIdYes
managementTokenNo

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses key behaviors: graduated=false and empty list for non-graduated drops, degraded=true meaning unknown rather than nothing published, newest-first ordering, and the currently served version. It also clarifies the managementToken rule for owned drops.

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 dense, front-loaded sentences: action/ordering, the level 1-3 edge case, and the degraded/auth caveats. No redundant phrases or filler.

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?

The description explains the important return distinctions (graduated, empty list, degraded) despite having no output schema. It is nearly complete, though it could name the exact version object fields returned; the current information is sufficient for invoking the tool correctly.

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?

With 0% schema description coverage, the description compensates for managementToken by explaining when it is unnecessary, and ties dropId to the drop/app being listed. It does not fully define every parameter, but the schema's pattern and the tool title cover the rest.

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?

The description begins with a specific verb and resource: list published versions of a GRADUATED app, newest first, with the currently served one. It also distinguishes this from the no-history behavior of levels 1-3, so an agent can separate it from sibling tools like list or status.

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 gives explicit when-not guidance: levels 1-3 have no history because replace overwrites the same key, and explains the degraded/empty-list semantics. It does not name an alternative sibling tool, so it falls just short of full alternative routing.

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

All Dropyour toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools target clearly distinct resources and actions, and descriptions do a good job separating overlapping areas like call/release/status or read_content/read_app_files. The main risk is momentary confusion between publish/replace/release and the two read-content tools, but careful reading resolves it.

Naming Consistency3/5

All names share the dropyour_ prefix and use snake_case, but the overall pattern is mixed: read_* and list_versions use verb-first naming, while records_list, secret_set, secret_delete, and secrets_list use noun-first naming, and logs/status/whoami are bare nouns. Still readable, but not a consistent verb_noun convention.

Tool Count3/5

23 tools is on the heavy side for a single server and spans several distinct subdomains: drop lifecycle, graduated apps, data, records, secrets, scheduling, and auth. Each tool appears purposeful, but the surface could reasonably be split into focused servers.

Completeness5/5

The set covers the full drop lifecycle — publish, replace, release, rollback, delete, status, settings — plus graduated app concerns like files, logs, versions, store records, app data, secrets, and scheduling. There are no obvious dead ends for the stated domain.

Resources