Skip to main content
Glama
Pixifi MCP Server

Pixifi MCP Server

pixifi_click

Clicks a numbered element on the current Pixifi page to select or navigate controls, using the element number from the last read.

Instructions

Click a numbered element on the current Pixifi 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": "pixifi_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/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 burden and discloses almost nothing behavioral. It does not say whether clicking navigates to a new page, whether it is reversible, whether it can trigger form submission or destructive UI actions, or whether element numbers become stale afterward.

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 or redundancy. It is efficient, though the brevity edges into under-specification rather than crisp completeness.

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

Completeness2/5

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

This is an action tool with no annotations and no output schema, and the description omits the things an agent most needs: that element numbering depends on a prior read and that the page state may change after the click. For a UI-mutating operation, the definition is too thin.

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 100% and the schema already explains the element number comes "from the last read." The description's "numbered element" phrasing is consistent but adds no syntax, range, or invalidation detail beyond the schema, 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 and target ("Click a numbered element") plus the scoping context "on the current Pixifi page," which is enough for an agent to identify the action. It does not explicitly contrast with siblings like pixifi_type or pixifi_read, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says to call pixifi_read first to obtain element numbers, nothing says when to prefer pixifi_type over a click, and no prerequisites or exclusions are stated. Usage is only implied by the words "numbered element."

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