originality-mcp

originality_get_scan_results

Retrieve stored scan results using a scan ID. Access previous originality checks when storeScan was enabled.

Instructions

Retrieve previously stored scan results by scan ID. Only works for scans that had storeScan set to true.

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": {
      "scanId": "<scanId>"
    },
    "name": "originality_get_scan_results"
  }
}

Input Schema

Name	Required	Description	Default
`scanId`	Yes	The privateID of the scan to retrieve results for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Discloses the critical behavioral condition (storeScan required) beyond the schema. With no annotations, this adds transparency. Could mention error handling or auth needs.

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, no wasted words. Information is front-loaded and easy to parse.

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?

Covers purpose and condition. Lacks output format or error cases, but given single param and no output schema, it's minimally adequate. Could be more complete.

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 already describes scanId as 'The privateID'. Description adds no further meaning to the parameter itself, just the condition. Baseline 3 due to 100% schema coverage.

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 it retrieves stored scan results by scan ID, with a key condition (storeScan=true). It distinguishes from siblings like originality_scan which likely creates scans, and originality_batch_scan.

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?

Explicitly says only works for scans that had storeScan set to true, guiding when to use. Could further indicate when to use alternatives like originality_scan if not stored.

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

Deploy Server