Skip to main content
Glama
Sign In
Foto MCP Server

Foto MCP Server

by thesven
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

foto_draft_post

Preview and validate a photo post draft without publishing; checks 1–3 whitelisted tags, formats EXIF summaries, and verifies image parameters before upload.

Instructions

Preview and validate a post draft without publishing. Validates tag constraints (1-3 from whitelist), formats EXIF summary, and checks image parameters.

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": {
      "filePath": "<filePath>",
      "caption": "<caption>",
      "tags": "<tags>"
    },
    "name": "foto_draft_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsYes1 to 3 tags chosen from Foto's curated list
captionYesThe post caption or narrative description
filePathYesAbsolute file path to local image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that nothing is published and what is validated, giving real behavioral context. However, it does not say what happens when validation fails (error vs. report in return) or what the response contains, and no output schema exists to cover that gap.

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?

Two sentences, zero waste, with the differentiating constraint front-loaded before the list of checks. Well structured for an agent scanning for the right tool.

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 validation tool with no annotations and no output schema, the agent needs to know what success versus failure looks like. The description lists what gets checked but leaves the response contract and failure behavior unaddressed.

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%, so all three parameters, including the '1 to 3 tags from a curated list' constraint, are already documented in the schema. The description mostly restates the tag rule and notes that image parameters are checked from filePath, adding only marginal meaning beyond the structured fields.

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?

Specific verb+resource: preview and validate a post draft, with the key distinguishing fact 'without publishing' stated up front. It enumerates the checks (tag constraints, EXIF summary, image parameters), which separates it from foto_publish_post and foto_publish_series in the sibling list.

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?

The 'without publishing' clause implies this is the pre-flight check before publishing, but it never explicitly says to call it before foto_publish_post or names any alternative. Usage is inferred rather than stated, which is the minimum-viable level.

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

Deploy Server

Other Tools