Skip to main content
Glama
Sign In

Dropspace

by io.github.JCLVSH
OverviewDiscussionsAdmin

configure_autopilot

Destructive

create or update the autopilot config. merge semantics: only the fields you send change. enabling requires at least one platform with a connected account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "configure_autopilot"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoreview = drafts wait for approval; auto = publishes on schedule
enabledNoturn nightly runs on/off
formatsNocontent formats the engine may produce
run_hourNolocal hour the nightly run fires
timezoneNoIANA timezone, e.g. America/New_York
min_queueNoideas to keep queued
platformsNoplatforms to post on (must have connected accounts)
persona_idNovoice persona uuid (null to clear)
product_urlNoproduct link included in posts
media_sourceNowhere image and video posts get media: ai (generated), library (only the user's media library), mixed (library first, AI when nothing fits)
posting_timesNo
product_briefNowhat you're building, who it's for (max 2000 chars)
content_pillarsNothemes the engine rotates across (max 10)
max_posts_per_dayNodaily posting cap
product_image_urlNoreference image for slideshow posts; omitted = filled from product_url's page when product_url changes; null clears it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, and the description usefully softens that by explaining merge semantics ('only the fields you send change'), which tells the agent partial updates are safe. It also discloses the enabling precondition. It does not say what is returned or what happens on invalid platform values.

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 short sentences, zero filler, with the merge-semantics constraint front-loaded before the enabling prerequisite.

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 15-parameter mutation tool with a nested object and no output schema, the description covers the two things the schema cannot: update semantics and the enabling precondition. Return behavior is the only notable omission, and no output schema exists to cover it.

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?

Schema description coverage is 93%, so the schema already documents all 15 parameters including enums and nested posting_times. The description adds no parameter-level detail beyond what the schema provides, 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 pair and resource: 'create or update the autopilot config'. An agent can distinguish this from get_autopilot or run_autopilot_now by the write semantics, 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?

Provides a real prerequisite ('enabling requires at least one platform with a connected account') and clarifies merge semantics, but gives no explicit when-to-use guidance versus alternatives such as run_autopilot_now or get_autopilot.

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

All Dropspace toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources