Skip to main content
Glama

Dropyour

by io.dropyour

Set how much this app's agent may do alone

dropyour_autonomy
Idempotent

Declare how much you delegate to the machine on ONE of your apps. Three modes. 'copilote' — nothing is autonomous: every call is a human gesture you are relaying, and everything your authority allows goes through. This is the state of every app until you delegate. 'jalons' — the machine acts alone on reads and on anything it can undo; structural decisions (graduating, stepping down) come back to you. 'autopilote' — it also decides structural moves alone. WHAT NO MODE EVER REACHES: an action nothing can undo — deleting a drop, deleting a secret. No delegation covers it, in any mode; that is what 'bounded' means here. Those are done from the cockpit, by the person who answers for them. Requires a connected account, never a management token: a token proves you hold this drop, not that you are the one answering for what a machine does next. Every change is filed, both ways.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYescopilote = nothing delegated (the default state).
dropIdYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare idempotentHint=true and destructiveHint=false, and the description adds substantial behavioral context beyond that: the exact boundaries of each mode, the irreversible actions no mode can delegate, the account-vs-token authentication constraint, and that every change is filed. This goes well beyond what annotations alone convey.

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?

Every sentence earns its place: purpose, default state, each mode's behavior, the bounded irreversible-action caveat, auth requirements, and logging. The structure front-loads the main purpose and then layers necessary nuance without repetition.

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 settings/mode-switching tool with two required parameters and no output schema, the description covers purpose, modes, boundaries, auth, and persistence. It does not describe the return value or success feedback, but that is a minor gap given how thoroughly the decision-relevant behavior is explained.

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 only 50% because dropId has no description beyond its pattern. The description compensates heavily for the mode parameter by explaining all three values in concrete behavioral terms. For dropId, the description implies it identifies the specific app ('ONE of your apps'), which combined with the schema pattern is sufficient albeit brief.

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 opens with a specific action and resource: 'Declare how much you delegate to the machine on ONE of your apps.' It clearly distinguishes this tool from siblings by focusing on per-app autonomy modes, not on calls, deletes, reads, or other operations.

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?

The description gives rich context for when to use the tool: setting one of three delegation modes for a single app, with a clear default state until delegation happens. It does not explicitly name alternatives or say 'use this instead of X', but the auth requirement ('never a management token') and the mode distinctions provide strong actionable guidance.

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