Skip to main content
Glama
Sign In

PicJury

by io.github.VKarich
OverviewDiscussionsAdmin

Start photo poll

start_photo_poll

Creates a PicJury photo poll: friends vote on which of 2 to 6 photos is best through one link, without signing up. For choices between photos (profile picture, dating photo, outfit, logo, thumbnail, product) that the user wants other people to decide. Photos attached in the chat are not passed to PicJury: the tool shows a PicJury card in which the user picks the photos and gets the vote link and a private link to follow the votes. question is what friends are asked, in the user's language; language sets the language of the PicJury 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": {
      "question": "<question>"
    },
    "name": "start_photo_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the PicJury page, the one the user writes in. Other languages: en.
questionYesWhat friends are asked, in the user's language. Example: "Which photo should be my profile picture?"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / language / enum
      Previous value: -[
-  "en",
-  "ja",
-  "ko",
-  "fr",
-  "es",
-  "de",
-  "it",
-  "pl",
-  "tr",
-  "id",
-  "vi",
-  "pt-BR",
-  "zh-CN",
-  "zh-TW",
-  "hi",
-  "sw",
-  "ha",
-  "am",
-  "ru",
-  "uk"
-]New value: +[
+  "en",
+  "ja",
+  "ko",
+  "fr",
+  "es",
+  "de",
+  "it",
+  "pl",
+  "tr",
+  "id",
+  "vi",
+  "ar",
+  "pt-BR",
+  "zh-CN",
+  "zh-TW",
+  "hi",
+  "sw",
+  "ha",
+  "am",
+  "ru",
+  "uk"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / language / enum
      Previous value: -[
-  "en",
-  "ja",
-  "fr",
-  "es",
-  "pt-BR",
-  "zh-CN",
-  "zh-TW",
-  "hi",
-  "sw",
-  "ha",
-  "am",
-  "ru",
-  "uk"
-]New value: +[
+  "en",
+  "ja",
+  "ko",
+  "fr",
+  "es",
+  "de",
+  "it",
+  "pl",
+  "tr",
+  "id",
+  "vi",
+  "pt-BR",
+  "zh-CN",
+  "zh-TW",
+  "hi",
+  "sw",
+  "ha",
+  "am",
+  "ru",
+  "uk"
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds real context on top: no signup for voters, an interactive PicJury card in chat, and two resulting links (vote link and private results link). It stops short of stating failure modes or that the poll link is externally shareable/long-lived, so not a 5.

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?

Front-loaded with the core action, and the parenthetical use-case list earns its place by disambiguating scope. The second sentence is dense but the third clarifies the photo handoff, which matters; only the 'question'/'language' restatement is slightly redundant.

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?

With two parameters, no output schema, and the description covering both the interactive card behavior and the two links returned, an agent has enough to call and explain the tool. Missing only detail on poll lifetime or what happens on failure.

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 both parameters are already documented in the schema, and the description largely restates them: 'question is what friends are asked, in the user's language' and 'language sets the language of the PicJury page'. It adds no format, default, or edge-case detail beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Starts with a specific verb and resource ('Creates a PicJury photo poll') and immediately defines the mechanism: friends vote on 2 to 6 photos through one link, no signup. The use-case list (profile picture, dating photo, outfit, logo, thumbnail, product) makes the tool's domain unmistakable.

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

Usage Guidelines5/5

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

Explicitly scopes when to use it — 'For choices between photos ... that the user wants other people to decide' — and adds a crucial exclusion: photos attached in the chat are not passed, the user selects them in the card. That is a genuine when/when-not instruction, and no siblings exist to route against.

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

All PicJury 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