Font Design MCP

Overview Schema Source Related Servers Discussions Admin

history_list

Read-onlyIdempotent

Retrieve committed project revisions with pagination, filtering by revision, offset, limit, and total count, while excluding uncommitted or interrupted stages.

Instructions

List committed revisions and summaries with pagination; interrupted uncommitted stages are excluded.

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`detail`	No	summary
`offset`	No
`revision`	No
`project_id`	Yes
`include_total`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`changed`	No
`summary`	Yes
`revision`	No
`warnings`	No
`project_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv0.4.3Sep 9, 2026
- addedInput schema / properties / detail
```
Added value: +{
+  "default": "summary",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / include_total
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / offset / title
```
Removed value: -"Offset"
```
- removedInput schema / properties / project_id / title
```
Removed value: -"Project Id"
```
- removedInput schema / properties / revision / title
```
Removed value: -"Revision"
```
- removedInput schema / title
```
Removed value: -"Page"
```
- removedOutput schema / properties / changed / title
```
Removed value: -"Changed"
```
- removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
- removedOutput schema / properties / error / title
```
Removed value: -"Error"
```
- removedOutput schema / properties / ok / title
```
Removed value: -"Ok"
```
- removedOutput schema / properties / project_id / title
```
Removed value: -"Project Id"
```
- removedOutput schema / properties / revision / title
```
Removed value: -"Revision"
```
- removedOutput schema / properties / summary / title
```
Removed value: -"Summary"
```
- removedOutput schema / properties / warnings / title
```
Removed value: -"Warnings"
```
- removedOutput schema / title
```
Removed value: -"Result"
```
First observedv0.1.0Sep 8, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds a meaningful behavioral detail: it excludes interrupted uncommitted stages, which is not inferable from annotations and helps the agent understand the tool's scope.

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 a single, front-loaded sentence that conveys purpose and a key exclusion without waste. It is appropriately concise for the tool's straightforward nature.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 parameters and 0% schema description coverage, the description is incomplete. It fails to explain parameter semantics, and while an output schema exists, the tool's behavior regarding filtering by revision or detail level is undocumented. The description is too sparse to fully guide correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for parameter meanings. It mentions pagination but does not explain limit, offset, detail, revision, include_total, or how they interact. The schema itself provides defaults and constraints but no descriptions, leaving the agent without guidance on parameter usage beyond names.

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 clearly states the tool lists committed revisions and summaries, with a specific exclusion of interrupted uncommitted stages. It uses a specific verb ('List') and resource, but does not explicitly differentiate from sibling tools like history_restore, though the purpose is unambiguous.

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 description implies usage for listing committed revisions only, and notes that uncommitted stages are excluded, which hints at when not to use it. However, it does not mention alternative tools or explicit when-to-use conditions, leaving some inference required.

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