Skip to main content
Glama
Sign In
picdrop MCP server

picdrop MCP server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

picdrop_click

Clicks a numbered element on the current Picdrop page so AI agents can navigate galleries, select images, or trigger page actions after reading available elements.

Instructions

Click a numbered element on the current picdrop page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "picdrop_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses little: it does not say whether clicking navigates, submits, or mutates page state, whether element numbering survives a click, or whether a re-read is required afterward. For an interaction tool whose side effects are the main risk, this is a meaningful gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. Its brevity is efficient, though it leaves no room for the precondition and post-condition details an agent would want.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, a short description is defensible, but it omits the two things that matter most: that the element number must come from a prior picdrop_read, and what a click does to page state. Adequate skeleton, incomplete for safe invocation.

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 coverage is 100% and the schema already explains "Element number from the last read," so the baseline is 3. The description's "numbered element" only loosely reinforces that the number corresponds to the current page listing, adding no syntax or range detail beyond the schema.

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 ("Click") and resource ("a numbered element on the current picdrop page"), which distinguishes it from picdrop_type and picdrop_read by action. It does not explicitly name a sibling, but the action alone is discriminative enough for selection.

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?

"On the current picdrop page" implies a page must already be open, which hints at the picdrop_open prerequisite, but the description never says so directly and offers no when-to-use vs when-not guidance (e.g., use picdrop_type for text entry instead of clicking).

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