Remote Camera

Server Details

Capture photos remotely from mobile devices via S3-backed upload URLs

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 61 days
Last Tested: 2026-10-17 02:22
Transport: Streamable HTTP · MCP 2025-06-18
URL

TDQS

A3.9/5.0

Scored 2026-10-08 03:40 across 2 tools

Disambiguation5/5

The two tools are cleanly split by phase: generate_upload_url handles the capture side while poll_for_upload handles retrieval. There is no overlap in purpose and the descriptions reinforce the handoff between them.

Naming Consistency5/5

Both names follow the same snake_case verb_object pattern (generate_upload_url, poll_for_upload), which is predictable and readable. No mixing of conventions.

Tool Count3/5

Two tools is borderline thin for the scope, though the workflow is genuinely just generate-then-poll. It earns a passing grade only because the domain is narrow; any expansion of camera control would immediately strain this surface.

Completeness4/5

The generate/poll pair covers the core capture-to-download lifecycle the server exists for. Minor gaps exist around cleanup, cancellation, or listing existing sessions, but agents can work around these for the primary use case.

Available Tools

2 tools

generate_upload_urlAInspect

Generate a URL for remote camera upload. Send this URL to a mobile device to capture and upload a photo. The capture URL can be reused multiple times to upload different photos without generating a new URL. The URL will be in format: https://www.ai.moda/mcp-servers/remote-camera/capture/?url=PRESIGNED_URL

ParametersJSON Schema

Name	Required	Description	Default
`message`	No	Instructions/message to display to the user on the capture page (max 200 characters)

Output Schema

ParametersJSON Schema

Name	Required	Description
`session_id`	Yes	Session ID used for this upload, in UUID format
`capture_url`	Yes	Full URL to send to mobile device for photo capture

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses reusability and the exact URL format, which is helpful. However, it does not mention any potential side effects, expiration, rate limits, or whether this creates a persistent record. For a generation tool with no annotations, this is adequate but not rich.

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?

Three concise sentences, each adding meaningful information. The description is front-loaded with the core action and includes practical format details without any fluff.

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?

For a simple single-parameter tool with an output schema, the description covers purpose, usage, reuse, and output format. It doesn't explicitly link to the sibling polling tool, so there is a small gap in the overall workflow, but the tool itself is well described.

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 schema description covers the 'message' parameter fully (instructions to display, max length), so the description adds only marginal value by implying the message is shown on the capture page. Baseline of 3 is appropriate given 100% schema coverage and no additional parameter details in the description.

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?

The description clearly states the verb 'Generate' and the resource 'URL for remote camera upload', and explains its purpose (sending to a mobile device for photo capture). It also explicitly distinguishes from the sibling tool 'poll_for_upload' by focusing on generation rather than polling.

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?

The description provides concrete usage context ('Send this URL to a mobile device to capture and upload a photo') and notes that the URL can be reused. It doesn't explicitly mention poll_for_upload as an alternative or next step, so it stops short of full exclusions, but the context is clear.

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

poll_for_uploadInspect

Poll S3 bucket waiting for photo upload to complete. Returns a presigned download URL when the file is ready. The same session_id can be used to poll for new uploads multiple times, allowing the capture URL to be reused.

ParametersJSON Schema

Name	Required	Description
`timeout`	No	Max seconds to wait for upload
`not_etag`	No	Only detect files with different ETag than this value, used to poll for new uploads
`session_id`	Yes	Session ID to poll for, in UUID format
`modified_since`	No	Only detect files modified after this date in ISO 8601 or HTTP date format

Output Schema

ParametersJSON Schema

Name	Required	Description
`etag`	Yes	ETag of the uploaded file, can be used with not_etag parameter for subsequent polls
`download_url`	Yes	Presigned GET URL to download the uploaded photo, valid for 7 days
`last_modified`	No	Last modified timestamp of the uploaded file from S3