Skip to main content
Glama
Sign In

Mart402

by com.mart402
OverviewDiscussionsAdmin

Portrait Analysis

portrait_analysis
Idempotent

Personal color analysis from 1-3 portraits: measured pixel colorimetry (CIELAB/ITA) cross-checked against vision-model attributes, cross-photo lighting consistency, then a published deterministic rule table gives the 4-season verdict with palette and style advice. No identification; images not stored. Flat $0.05/call. Choose this when you need only the seasonal color verdict and palette as JSON. For the fuller styling verdict (face impression, body frame, silhouette) use style_profile; for a finished PDF for a human client use style_report.

Input Schema

NameRequiredDescriptionDefault
styleNoOne of: feminine, masculine, neutral. Styling context: feminine, masculine or neutralneutral
imagesNoup to 3 of {image_url|image_base64}; different lighting recommended
image_urlNoAbsolute http(s) URL of the image (JPEG/PNG/WebP)
pack_codeNoretry credit issued after an unbilled failed call (replaces payment)
x_paymentNoOptional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged.
image_base64NoBase64-encoded image bytes (alternative to image_url)

Output Schema

NameRequiredDescriptionDefault
bodyYesJSON body of the underlying call (see /samples/{product} for each product's shape)
statusYesHTTP status of the underlying call (200 result, 402 payment terms, 4xx input error)
how_to_payNo
receipt_idNoset on paid results; free re-fetch via get_receipt
payment_requiredNotrue when status is 402: body holds x402 payment terms, not a result. Pay and call again with x_payment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / pack_code
      Added value: +{
+  "description": "retry credit issued after an unbilled failed call (replaces payment)",
+  "type": "string"
+}
    • addedInput schema / x-required-one-of
      Added value: +[
+  "image_url",
+  "image_base64",
+  "images"
+]
    • addedOutput schema / properties / how_to_pay
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / payment_required
      Added value: +{
+  "description": "true when status is 402: body holds x402 payment terms, not a result. Pay and call again with x_payment",
+  "type": "boolean"
+}
    • addedOutput schema / properties / receipt_id
      Added value: +{
+  "description": "set on paid results; free re-fetch via get_receipt",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "body": {
+      "description": "JSON body of the underlying call (see /samples/{product} for each product's shape)"
+    },
+    "status": {
+      "description": "HTTP status of the underlying call (200 result, 402 payment terms, 4xx input error)",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "status",
+    "body"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / style / description
      Previous value: -"Styling context: feminine, masculine or neutral"New value: +"One of: feminine, masculine, neutral. Styling context: feminine, masculine or neutral"
  4. Changed3 schema fields changed
    • addedInput schema / properties / image_base64 / description
      Added value: +"Base64-encoded image bytes (alternative to image_url)"
    • addedInput schema / properties / image_url / description
      Added value: +"Absolute http(s) URL of the image (JPEG/PNG/WebP)"
    • addedInput schema / properties / style / description
      Added value: +"Styling context: feminine, masculine or neutral"
  5. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing cost ($0.05/call), the x402 payment handshake (omitting x_payment returns payment requirements without being charged), retry-credit behavior via pack_code, and privacy guarantees ('no identification; images not stored'). It also flags cross-photo lighting consistency as part of processing, which an agent needs in order to submit valid inputs. Nothing here contradicts the readOnlyHint/openWorldHint/idempotentHint annotations.

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?

The method, cost, and privacy caveats are front-loaded before the routing sentence, and every sentence carries information. It is dense — the first sentence packs method, pipeline, and output into one clause — but not padded.

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?

An output schema exists, so return shape needn't be restated, and the description still names the verdict and palette contents. Combined with the payment mechanics, privacy statement, input-count guidance, and sibling routing, an agent has everything needed to call this correctly.

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 schema already documents every parameter, and the description only echoes the '1-3 portraits' shape and the purpose of multi-image input. It adds marginal semantics (why multiple photos help) but no format or validation detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ('personal color analysis from 1-3 portraits') and explains the mechanism (CIELAB/ITA colorimetry cross-checked with vision-model attributes, deterministic rule table). It also explicitly names the sibling tools it is not, so an agent can distinguish it from style_profile and style_report without opening any schema.

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?

Gives an explicit selection rule: 'Choose this when you need only the seasonal color verdict and palette as JSON,' then routes the two alternative needs to style_profile (fuller styling verdict) and style_report (PDF for a human client). When-to-use, when-not-to-use, and alternatives are all present.

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

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