Suparse MCP Server

Official

by suparse

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

List Templates

list_templates

Read-onlyIdempotent

Discover extraction templates for document processing, compare team options, and retrieve template IDs to pass to extraction tools. View full schemas and prompts; system templates are discovery-only.

Instructions

Discover extraction templates; defaults to compact summary view with team templates only. Prefer a matching active team template and pass its id as template_id to extraction tools. Use view full to inspect schema and prompts. include_system true adds discovery-only system templates; MCP cannot add them to the team or use their IDs directly. If no template matches, omit template_id for auto-detection or use start_quick_schema_creation when schema creation is authorized. This tool does not create or modify templates.

Input Schema

Name	Required	Description	Default
`view`	No	Template response view. Summary is compact and recommended for normal template selection; full includes schema, prompts, validation rules, and creator metadata.	summary
`api_url`	No
`include_system`	No	Defaults to false. Include discovery-only system templates in addition to team templates. Do not pass system template IDs to extraction tools. MCP cannot add system templates to the team; omit template_id for auto-detection or use an authorized quick-schema workflow instead.

Output Schema

Name	Required	Description	Default
`templates`	Yes
`agent_guidance`	Yes
`team_templates`	Yes
`system_templates`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv1.5.0Oct 20, 2026

removedInput schema / properties / api_url / description

Removed value: -"Optional API base URL. Defaults to SUPARSE_API_URL or Suparse production API."

removedInput schema / properties / api_url / format
```
Removed value: -"uri"
```
addedInput schema / properties / api_url / not
```
Added value: +{}
```
removedInput schema / properties / api_url / type
```
Removed value: -"string"
```

changedInput schema / properties / include_system / description

Previous value: -"Include discovery-only system templates in addition to team templates. System templates returned here are not directly usable for extraction through MCP until the user adds them to their templates in the Suparse UI."New value: +"Defaults to false. Include discovery-only system templates in addition to team templates. Do not pass system template IDs to extraction tools. MCP cannot add system templates to the team; omit template_id for auto-detection or use an authorized quick-schema workflow instead."

addedInput schema / properties / view

Added value: +{
+  "default": "summary",
+  "description": "Template response view. Summary is compact and recommended for normal template selection; full includes schema, prompts, validation rules, and creator metadata.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}

removedOutput schema / properties / system_templates / items / $ref
```
Removed value: -"#/properties/templates/items"
```

addedOutput schema / properties / system_templates / items / anyOf

Added value: +[
+  {
+    "$ref": "#/properties/templates/items/anyOf/0"
+  },
+  {
+    "$ref": "#/properties/templates/items/anyOf/1"
+  }
+]

removedOutput schema / properties / team_templates / items / $ref
```
Removed value: -"#/properties/templates/items"
```

addedOutput schema / properties / team_templates / items / anyOf

Added value: +[
+  {
+    "$ref": "#/properties/templates/items/anyOf/0"
+  },
+  {
+    "$ref": "#/properties/templates/items/anyOf/1"
+  }
+]

removedOutput schema / properties / templates / items / additionalProperties
```
Removed value: -false
```

addedOutput schema / properties / templates / items / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "created_at": {
+        "type": "string"
+      },
+      "description": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "type": "string"
+      },
+      "is_active": {
+        "type": "boolean"
+      },
+      "is_system_template": {
+        "type": "boolean"
+      },
+      "name": {
+        "type": "string"
+      },
+      "parent_template_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "team_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "template_group_id": {
+        "type": "string"
+      },
+      "template_language": {
+        "type": "string"
+      },
+      "version": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "template_language",
+      "template_group_id",
+      "version",
+      "is_active",
+      "is_system_template",
+      "created_at"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "created_at": {
+        "$ref": "#/properties/templates/items/anyOf/0/properties/created_at"
+      },
+      "created_by_user_id": {
+        "type": "string"
+      },
+      "description": {
+        "$ref": "#/properties/templates/items/anyOf/0/properties/description"
+      },
+      "id": {
+        "$ref": "#/properties/templates/items/anyOf/0/properties/id"
+      },
+      "is_active": {
+        "$ref": "#/properties/templates/items/anyOf/0/properties/is_active"
+      },
+      "is_system_template": {
+        "$ref": "#/properties/templates/items/anyOf/0/properties/is_system_template"
+      },
+      "name": {
+        "$ref": "#/properties/templates/items/anyOf/0/properties/name"
+      },
+      "parent_template_id": {
+        "$ref": "#/properties/templates/items/anyOf/0/properties/parent_template_id"
+      },
+      "prompt_set": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "saved_document_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "schema_definition": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "team_id": {
+        "$ref": "#/properties/templates/items/anyOf/0/properties/team_id"
+      },
+      "template_group_id": {
+        "$ref": "#/properties/templates/items/anyOf/0/properties/template_group_id"
+      },
+      "template_language": {
+        "$ref": "#/properties/templates/items/anyOf/0/properties/template_language"
+      },
+      "validation_rules": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "version": {
+        "$ref": "#/properties/templates/items/anyOf/0/properties/version"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "template_language",
+      "template_group_id",
+      "version",
+      "is_active",
+      "is_system_template",
+      "created_at",
+      "schema_definition",
+      "prompt_set",
+      "validation_rules",
+      "created_by_user_id"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties / templates / items / properties

Removed value: -{
-  "created_at": {
-    "type": "string"
-  },
-  "description": {
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "id": {
-    "type": "string"
-  },
-  "is_active": {
-    "type": "boolean"
-  },
-  "is_system_template": {
-    "type": "boolean"
-  },
-  "name": {
-    "type": "string"
-  },
-  "template_language": {
-    "type": "string"
-  },
-  "version": {
-    "type": "number"
-  }
-}

removedOutput schema / properties / templates / items / required

Removed value: -[
-  "id",
-  "name",
-  "template_language",
-  "version",
-  "is_active",
-  "is_system_template",
-  "created_at"
-]

removedOutput schema / properties / templates / items / type
```
Removed value: -"object"
```

First observedv1.3.0Jul 30, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, and the description stays consistent with them ('does not create or modify templates'). It adds genuine behavioral context beyond annotations: system templates are discovery-only, MCP cannot add them to the team or use their IDs directly, and when authorized schema creation is the fallback path.

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?

Front-loaded with the core purpose and default behavior, then layers routing guidance and constraints. Every clause carries information, though the dense run of conditional instructions (auto-detection, quick-schema fallback, system-template caveat) is packed tightly for a small tool.

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?

Output schema exists, so return-value explanation is unnecessary, and the description fully covers what an agent needs: selection workflow, the summary/full distinction, system-template limitations, and the no-match fallback. Complete for this tool's role as the entry point to the extraction workflow.

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 67% and the schema already documents view (summary vs full) and include_system fairly fully. The description reinforces with usage-oriented meaning ('Use view full to inspect schema and prompts', include_system adds discovery-only templates), but mostly restates rather than introducing new semantics.

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?

States a specific verb+resource ('Discover extraction templates') plus scope ('defaults to compact summary view with team templates only'). Immediately distinguishes it from the sibling extraction/creation tools by framing it as discovery only, ending with 'This tool does not create or modify templates.'

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?

Explicit when-to-use logic: prefer a matching active team template and pass its id as template_id to extraction tools; if none matches, omit template_id for auto-detection or use start_quick_schema_creation when schema creation is authorized. It names specific alternatives and the conditions that select them.

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

Deploy Server