Skip to main content
Glama

Get the markdown format

get_markdown_spec
Read-onlyIdempotent

The full markdown format md2pdf accepts: markdown features, signature lines, fill-in fields, styles and limits.

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": "get_markdown_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the response covers specific content categories, which is real value since there is no output schema, but it does not state the return form (documentation text vs. structured sections) or its size.

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?

A single compact clause with the subject front-loaded and zero filler. It is a noun phrase rather than a sentence, which slightly reduces immediate clarity about what the call actually returns.

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 parameterless read-only reference tool with full annotation coverage, the definition supplies the essential information: what the spec contains and by implication that it is the authoritative format for md2pdf. The only gap is that, absent an output schema, it never states the shape of the returned document.

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?

Zero parameters, so there is nothing to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no inputs are needed to retrieve the spec.

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: the markdown format md2pdf accepts, and enumerates the content it covers (markdown features, signature lines, fill-in fields, styles and limits). It is clearly a reference/spec retrieval tool, distinct from validate_markdown, render_pdf and send_for_signature. It stops short of an explicit verb like 'returns documentation for', which is why it is not a 5.

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?

Usage is only implied: 'the format md2pdf accepts' suggests consulting this before authoring or validating markdown. There is no explicit when-to-use statement, no mention of consulting it before render_pdf or validate_markdown, and no 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.