Retrieve recently opened folders from Typora's history to quickly locate and resume work on past projects without navigating manually.
Retrieve recently opened workspaces and folders from Typora's history.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of recent folders to return (default: 20). |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It states a read operation ('Retrieve') but does not disclose details like ordering, whether the current workspace is included, or if the result is limited to only folders. However, the behavior is simple and the description is not misleading, so a mid-score is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that front-loads the action and resource. There is no wasted wording, and it is easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple retrieval tool with one optional parameter and no output schema, the description is sufficiently complete. It tells the agent what the tool returns (recent folders/workspaces) and does not omit critical details. A minor gap is that it doesn't specify if the history is sorted, but that is not essential for correctness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already fully documents the 'limit' parameter with a default and meaning. The description adds no extra value beyond the schema, so the baseline of 3 is correct.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Retrieve' and the resource 'recently opened workspaces and folders from Typora's history'. It is specific enough to distinguish from sibling typora_recent_documents by mentioning workspaces and folders, which are different from documents.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the use case (when you need recent folders/workspaces), but it does not explicitly mention when NOT to use it or point to an alternative like typora_recent_documents. No guidance on selecting between similar sibling tools is provided, leaving it to the agent to infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.