Skip to main content
Glama
Pixifi MCP Server

Pixifi MCP Server

pixifi_read

Read the current Pixifi page to extract visible text and numbered buttons, links, and fields; specify an element to limit reading to that section.

Instructions

Read the current Pixifi 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": "pixifi_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full disclosure burden, and it does add real value by specifying the returned content types (text, numbered buttons, links, fields). It says nothing about snapshot freshness, page size limits, truncation, or whether reading has side effects, which leaves meaningful behavioral gaps for an unannotated tool.

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 short sentence, front-loaded with the verb and resource, followed immediately by the returned content. No filler or redundancy.

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 simple one-optional-parameter read tool with no annotations or output schema, the description covers purpose and return contents adequately. It falls short only on exploration guidance (when to read vs. status/open/guide), which is minor given the tool's simplicity.

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 'element' parameter already documents its meaning ('Read only inside this element'). The description adds no scoping detail such as how element indices are obtained or what happens if the element is off-screen, so the schema 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?

The description names a specific verb ('Read') and resource ('the current Pixifi page') and enumerates what comes back: text, numbered buttons, links and fields. That is enough to distinguish it from write-oriented siblings such as pixifi_click and pixifi_type, 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?

Usage is only implied. Mentioning 'numbered buttons' hints that this is the inspection step that precedes a numbered pixifi_click, but the description never states when to call this instead of pixifi_status, pixifi_guide, or pixifi_open, and gives no preconditions.

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