Skip to main content
Glama
Sign In

Pixelworkers

by org.pixelworkers
OverviewDiscussionsAdmin

Get a fixed price from Pixelworkers

start_a_quote
Read-onlyIdempotent

For someone who wants Pixelworkers to do a job. Returns a link to pixelworkers.org that opens the quote chat with the job already typed in; they send it and get a fixed, scoped price in minutes. Nothing is submitted from here.

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": {
      "job": "<job>"
    },
    "name": "start_a_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesThe job in the person's own words, e.g. 'a new website for my dental practice, about six pages, with online booking'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond them by explaining that it only returns a link, the user must send the chat themselves, and 'Nothing is submitted from here,' reinforcing that no side effect occurs. It stops short of covering link expiration or rate limits.

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?

The description is compact and front-loaded: it identifies the audience, states the return value, explains the follow-up flow, and closes with an important caveat. Every sentence contributes useful information.

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

Completeness5/5

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

With one fully documented parameter, rich annotations, and no output schema, the description supplies the necessary missing context: it explains the return value (a link) and the user-facing next step. Nothing essential for correct invocation appears to be missing.

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%, so the single 'job' parameter is already fully documented with an example. The description reinforces that the job is pre-typed into the chat but adds no syntax or formatting details 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?

The description states a specific action: it returns a link to pixelworkers.org that opens a pre-filled quote chat. This clearly distinguishes the tool from generic siblings like fetch, search, and get_services, though it does not explicitly name or contrast those alternatives.

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?

It gives an implied usage context ('For someone who wants Pixelworkers to do a job') but does not explicitly say when to use this tool versus siblings such as get_services or search, nor does it provide when-not guidance.

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

All Pixelworkers toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources