GoCertius MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

dossier_evidence_link

Link evidence items to a DRAFT dossier using UUIDs. Prepare the dossier for certification by calling dossier_certify after linking.

Instructions

Links specific evidence items to a DRAFT dossier. Call once per case file containing evidences to link. After linking all evidences, call dossier_certify to finalize. For a single-group dossier, use dossier_group_certify instead (one step). Example: dossier_evidence_link({ caseFileId: '...', dossierId: '...', caseFileToLinkId: '...', ids: ['ev-uuid-1', 'ev-uuid-2'] })

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": {
      "caseFileId": "<caseFileId>",
      "dossierId": "<dossierId>",
      "caseFileToLinkId": "<caseFileToLinkId>",
      "ids": "<ids>"
    },
    "name": "dossier_evidence_link"
  }
}

Input Schema

Name	Required	Description
`ids`	Yes	UUIDs of the evidence items to link
`dossierId`	Yes	UUID of the DRAFT dossier to link evidences to
`caseFileId`	Yes	UUID of the case file that owns the dossier
`caseFileToLinkId`	Yes	UUID of the case file containing the evidences (often same as caseFileId)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.1Jul 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds context beyond annotations by specifying the requirement for a DRAFT dossier and the sequential calling pattern. It does not contradict annotations, but could further disclose behavior for non-draft dossiers or duplicate links.

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 plus a concise example front-load the essential information with no extraneous content, achieving high efficiency.

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?

The description covers the workflow linking to dossier_certify and dossier_group_certify, but does not explain the return value or error conditions. Given the tool's simplicity, it is reasonably 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?

Schema description coverage is 100%, so baseline is 3. The description adds an example but does not provide additional semantic meaning beyond what the schema already documents for each parameter.

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 links evidence items to a DRAFT dossier, distinguishing it from sibling tools like dossier_group_certify and providing a specific verb-resource combination.

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?

Explicitly instructs to call once per case file, then use dossier_certify to finalize, and advises using dossier_group_certify for single-group dossiers, offering clear when-to-use and when-not-to-use guidance.

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