Skip to main content
Glama

Import Markdown

import_markdown
Read-only

Convert Markdown (with optional YAML front matter, GFM tables, math and directives) into a Publisle document.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "markdown": "<markdown>"
    },
    "name": "import_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
markdownYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond parsing features: it does not say whether a persisted document is created (which is ambiguous given readOnlyHint=true), whether repeated calls duplicate documents despite idempotentHint=false, or how malformed Markdown/front matter is handled.

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?

A single sentence with the conversion statement front-loaded and the supported-syntax caveats compressed into a parenthetical. No filler or redundant restatement of the title.

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

Completeness3/5

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

For a one-parameter tool with no output schema, the description covers the input side adequately but leaves the result undefined: it never says whether the call returns a new document, an identifier, or a parsed tree, which matters because readOnlyHint=true rules out straightforward persistence. That missing return-shape note is the main completeness gap.

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?

Only one parameter with 0% schema coverage, but the description compensates by naming it implicitly ('Markdown') and specifying the accepted constructs: optional YAML front matter, GFM tables, math, and directives. That tells an agent what may legitimately go into the string, which is more than the bare 'string' schema conveys.

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 concrete verb and resource: 'Convert Markdown ... into a Publisle document,' and enumerates the accepted input dialects (YAML front matter, GFM tables, math, directives). That is clearly distinct from export_markdown (reverse direction) and import_json (different input format), though it never explicitly contrasts itself with content-adding siblings such as new_document or add_block.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when this tool should be chosen over alternatives. An agent must guess whether to use import_markdown versus new_document, add_block, or import_json when ingesting content, and there are no stated preconditions or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources