Lumethic Photo Verification

get_verification

Read-onlyIdempotent

Retrieve a verification by id: processing status and per-algorithm authenticity results. Completed single-image (image_only) verifications also include a verdict and a structured evidence_report with per-check findings and coverage. While the analysis is still running (status pending, queued or in_progress) the call waits for it, up to wait_seconds (default and maximum 40; pass 0 to return immediately), and answers as soon as it completes. A non-final response includes waited_seconds, expected_wait and next_step: call again and keep calling until status is completed or failed. Analysis takes from about a minute to 10 minutes or more, so expect several calls. Under heavy load the server may skip the wait and answer at once; the status is still correct, just call again. Scoped to the caller's account.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`wait_seconds`	No	Seconds to wait for a running analysis before answering (0-40, default 40; values above 40 are capped). The call returns early as soon as the verification completes, and immediately when it is already completed or failed. 0 disables waiting.
`verification_id`	Yes	Verification id (UUID) as returned by verify_photo, verify_content_credentials or list_verifications.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 8, 2026

addedInput schema / properties / wait_seconds

Added value: +{
+  "default": 40,
+  "description": "Seconds to wait for a running analysis before answering (0-40, default 40; values above 40 are capped). The call returns early as soon as the verification completes, and immediately when it is already completed or failed. 0 disables waiting.",
+  "title": "Wait Seconds",
+  "type": "integer"
+}

Changed1 schema field changedSep 8, 2026

addedInput schema / properties / verification_id / description

Added value: +"Verification id (UUID) as returned by verify_photo, verify_content_credentials or list_verifications."

First observedJul 25, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing wait behavior, wait_seconds semantics, early-return conditions under heavy load, the non-final response fields (waited_seconds, expected_wait, next_step), and the range of possible statuses. This is exactly the behavioral context an agent needs to poll correctly.

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 dense but every sentence earns its place: result scope, completion extras, wait behavior, polling loop, duration expectations, load behavior, and account scoping. It is front-loaded with the core purpose and then expands into operational details.

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?

For a read-only polling tool with an output schema, the description covers the full invocation lifecycle: what to expect initially, how long to wait, what fields indicate non-completion, when to call again, and how to handle server-side wait skipping. Nothing needed for correct usage is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds useful context on top: it explains what wait_seconds does in practice, how returning early works, and what a non-final response contains. This supplements the schema without repeating it.

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 names a specific verb and resource ('Retrieve a verification by id') and explains what the response contains (status, per-algorithm results, verdict for completed image_only verifications). It is clearly distinct from list_verifications by requiring a verification_id, but it does not explicitly name or contrast a sibling tool.

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?

Provides explicit polling guidance: call again and keep calling until status is completed or failed, expect several calls because analysis takes 1-10 minutes, and handle early returns under load. It does not explicitly say when to use this tool versus listing or creating verifications, but the polling workflow is well covered.

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

All Lumethic Photo Verification tools Inspect

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

Need Help?