Skip to main content
Glama
Pixifi MCP Server

Pixifi MCP Server

pixifi_guide

Learn how to navigate Pixifi screens and locate the sign-in link so you can manage photography studio clients, leads, proposals, contracts, events, and invoices.

Instructions

How to work in Pixifi (photography studio clients, leads, proposals, contracts, events and invoices): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Pixifi, in your words.

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, the description must carry the whole behavioral burden. It implies a read-only orientation call and instructs ordering, but never states that it has no side effects, requires no authentication itself, or that the sign-in link leads to a separate auth step the agent must handle. Those are exactly the behaviors an agent needs for a 'call first' tool.

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?

Two tight sentences with the ordering cue front-loaded and zero filler. The parenthetical entity list is dense but each item earns its place by scoping the guide's coverage.

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, no-annotation, no-output-schema tool, the definition should at least characterize the shape of what comes back (step-by-step instructions? screen map?). It hints at content with 'screens and the sign-in link' but leaves the return form implicit, which is the main remaining gap.

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?

The single 'task' parameter has 100% schema description coverage, so the baseline is 3. The description adds nothing about how to phrase the task or what granularity of task yields useful guidance, so it does not exceed 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?

The description names the resource (Pixifi, a photography studio system) and enumerates the domain objects it covers (clients, leads, proposals, contracts, events, invoices), plus the concrete artifacts it supplies: screens and the sign-in link. It is clearly an orientation/guidance tool rather than one of the browser-action siblings (click, type, read), so an agent can separate it. It stops short of saying explicitly that it returns instructional text, which keeps it from 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 Guidelines4/5

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

"Call this first" is an explicit, actionable ordering directive that tells the agent exactly when to invoke it relative to other tools. What is missing is any when-not guidance or a stated handoff to specific siblings after reading the guide.

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