med-lit-mcp

Overview Schema Source Related Servers Discussions Admin

record_synthesis

Destructive

Save or update an entity synthesis page from next_synthesis, replacing stored content with a new page or only changed sections to keep medical literature reviews evidence-linked.

Instructions

Save an entity page from next_synthesis, replacing the stored one: a new page, or only the changed sections of an update. Rules: guide("synthesis").

Input Schema

TableJSON Schema

Name	Required	Description
`project`	No	Project name from list_projects; may be omitted when only one project exists
`summary`	No	2-3 sentence overview; for an update only if it changes
`sections`	No	Update: only the changed sections, as {heading: full new section text}; an empty text removes a section
`entity_id`	Yes	From next_synthesis
`synthesis`	No	New page: Markdown with '## ' sections, citing sources as [uid] and linking entities as [[Name]]
`key_aspects`	No
`input_digest`	Yes	From next_synthesis
`related_entities`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.10Oct 17, 2026
- addedInput schema / properties / entity_id / description
```
Added value: +"From next_synthesis"
```
- addedInput schema / properties / input_digest / description
```
Added value: +"From next_synthesis"
```

Changed25 schema fields changedv0.1.5Oct 1, 2026

addedInput schema / properties / key_aspects / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 10,
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / key_aspects / default
```
Added value: +null
```
removedInput schema / properties / key_aspects / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / key_aspects / maxItems
```
Removed value: -10
```
removedInput schema / properties / key_aspects / minItems
```
Removed value: -1
```
removedInput schema / properties / key_aspects / type
```
Removed value: -"array"
```

addedInput schema / properties / related_entities / anyOf

Added value: +[
+  {
+    "items": {
+      "$ref": "#/$defs/RelatedEntity"
+    },
+    "maxItems": 30,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / related_entities / default
```
Added value: +null
```
removedInput schema / properties / related_entities / items
```
Removed value: -{
-  "$ref": "#/$defs/RelatedEntity"
-}
```
removedInput schema / properties / related_entities / maxItems
```
Removed value: -30
```
removedInput schema / properties / related_entities / type
```
Removed value: -"array"
```

addedInput schema / properties / sections

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Update: only the changed sections, as {heading: full new section text}; an empty text removes a section",
+  "title": "Sections"
+}

addedInput schema / properties / summary / anyOf

Added value: +[
+  {
+    "maxLength": 800,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / summary / default
```
Added value: +null
```

changedInput schema / properties / summary / description

Previous value: -"2-3 sentence overview"New value: +"2-3 sentence overview; for an update only if it changes"

removedInput schema / properties / summary / maxLength
```
Removed value: -800
```
removedInput schema / properties / summary / minLength
```
Removed value: -1
```
removedInput schema / properties / summary / type
```
Removed value: -"string"
```

addedInput schema / properties / synthesis / anyOf

Added value: +[
+  {
+    "maxLength": 20000,
+    "minLength": 200,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / synthesis / default
```
Added value: +null
```

changedInput schema / properties / synthesis / description

Previous value: -"Markdown article citing sources as [uid] and linking entities as [[Name]]"New value: +"New page: Markdown with '## ' sections, citing sources as [uid] and linking entities as [[Name]]"

removedInput schema / properties / synthesis / maxLength
```
Removed value: -20000
```
removedInput schema / properties / synthesis / minLength
```
Removed value: -200
```
removedInput schema / properties / synthesis / type
```
Removed value: -"string"
```

changedInput schema / required

Previous value: -[
-  "entity_id",
-  "input_digest",
-  "summary",
-  "synthesis",
-  "key_aspects",
-  "related_entities"
-]New value: +[
+  "entity_id",
+  "input_digest"
+]

First observedv0.1.1Sep 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false, and the description reinforces this by stating it is 'replacing the stored one' rather than appending. That is genuine added context about what gets destroyed, though it omits auth/permission prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the replace semantics and mode distinction front-loaded. The trailing 'Rules: guide("synthesis").' is terse but earns its place as a routing pointer.

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?

With an output schema present and annotations covering the safety profile, the description does not need to explain return values and mostly does not. It supplies the replace/mode context an agent needs, leaving only permission and rules detail to the guide reference.

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 75%, so most parameters are already documented in the schema. The description adds the new-vs-update mode framing (mapping loosely to synthesis/sections) but contributes no syntax or format detail beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb (Save) and resource (an entity page from next_synthesis), and distinguishes the two modes: a new page versus only changed sections of an update. It implicitly separates itself from the sibling next_synthesis, which generates the content this tool persists.

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 phrase 'from next_synthesis' implies the tool is used after that sibling produces content, and 'Rules: guide("synthesis")' routes the agent to a rules source. However, it gives no explicit when/when-not conditions or named alternatives beyond these hints.

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