picdrop MCP server

picdrop_read

Reads the current Picdrop page to extract text and numbered interactive elements—buttons, links, and fields—or focuses on a specified element. Use it to inspect page content before acting.

Instructions

Read the current picdrop page: its text and numbered buttons, links and fields.

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": "picdrop_read"
  }
}

Input Schema

Name	Required	Description	Default
`element`	No	Read only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the observable result (text plus numbered buttons, links, fields), which is the key behavior an agent needs for follow-up indexed actions, but it says nothing about side-effect freedom, whether numbering is stable across reads, truncation, or how much page content is returned.

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?

A single front-loaded sentence with zero filler; the verb and resource come first and the payload description follows immediately.

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 one-parameter read tool with no annotations and no output schema, this covers the essentials, including what the caller gets back. It falls slightly short on prerequisites (an open page) and on how the returned numbering is meant to be consumed by downstream tools.

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 single optional parameter already documents itself as "Read only inside this element." The description adds no further meaning about element semantics (e.g., which numbers are valid, whether they come from a prior read), so the baseline of 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 ("Read") and resource ("the current picdrop page") and enumerates what is returned: text, numbered buttons, links and fields. That distinguishes it from the sibling mutation tools (picdrop_click, picdrop_type) without needing to name them, though it does not explicitly route to or away from any named alternative.

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 only implied: "the current ... page" hints that a page must already be open (via picdrop_open) and that this is the discovery step before clicking or typing. There is no explicit when-to-use, no when-not-to-use, and no stated relationship to picdrop_guide or picdrop_status.

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

Deploy Server