Skip to main content
Glama

What Tisty adds to Markdown

language
Read-onlyIdempotent

Look up Tisty's Markdown extension reference by topic—pens, callouts, folds, tags, diagrams—before writing notes or documents; omit topic for the index. Plain Markdown needs no lookup.

Instructions

Reference for the Markdown extensions Tisty reads, to look up before writing one: pens, underline, icons, callouts, folds, tags, cards, attachments, diagrams. Plain Markdown needs none. Without topic, the index; then ask only the topic you will write. How the app works is help.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "language"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen, the default, or es
topicNoOne part, named as the index names it, or all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.43.2
    • changedInput schema / properties / lang / description
      Previous value: -"en for English, es for Spanish. Left out, English"New value: +"en, the default, or es"
    • changedInput schema / properties / topic / description
      Previous value: -"One part of the guide, named as the index names it, or all for the whole of it. Left out, the index"New value: +"One part, named as the index names it, or all"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent, closed-world and non-destructive, so the safety profile is covered. Beyond that, the description adds genuine behavioral context: the no-`topic` call returns an index, and the intended pattern is a targeted follow-up call rather than dumping everything. It does not describe the shape of the returned reference material, leaving a small gap.

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?

It is short, front-loaded, and every clause carries instruction. The inline enumeration of extension types partially duplicates the `topic` enum in the schema, which is mild redundancy, and the telegraphic style ('Without `topic`, the index; then ask only...') takes a second read but does not obscure the point.

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?

For a zero-required-parameter, read-only reference lookup with no output schema, the description covers purpose, workflow ordering, exclusions, and the sibling alternative — enough for an agent to call it correctly. Only the nature of the returned content is left implicit, which is acceptable given the tool's simplicity.

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 100% with both enums documented, so the baseline is 3. The description earns above that by explaining the `topic` omission case (returns the index) and advising to 'ask only the topic you will write,' which is workflow meaning the enum list alone does not convey.

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 names the resource precisely ('Reference for the Markdown extensions Tisty reads') and enumerates the extension families covered (pens, underline, icons, callouts, folds, tags, cards, attachments, diagrams). The action verb is only implied via 'to look up before writing one' rather than stated outright, so it falls just short of a clean verb+resource statement. It does differentiate from a sibling by pointing app-behavior questions to `help`.

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?

It states when to use ('look up before writing one'), when not to ('Plain Markdown needs none'), and the alternative for a different need ('How the app works is `help`'). It also prescribes a concrete two-step workflow: call without `topic` for the index, then request only the section you will write.

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