Skip to main content
Glama

Get the md2sign markdown format

get_markdown_spec
Read-onlyIdempotent

Explains md2sign's markdown format: signature fields [[signature: First Last ]], optional roles, input fields signers fill in [[field: Label | for: email | type: date | required]], and hidden style/title/signing-order directives. Returns an example contract. Call this first if you have not written md2sign markdown before.

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

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds value beyond that by disclosing the return payload ('Returns an example contract') and enumerating what the format covers — signature fields, optional roles, input fields, and hidden style/title/signing-order directives — which is the substantive behavioral context an agent needs.

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?

Three sentences, each with a distinct job: what the format contains, what is returned, and when to call it. The embedded syntax examples are dense but load-bearing, and the call-first guidance is placed at the end where it functions as the action cue without burying the purpose.

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?

With no input parameters and no output schema, the description carries the burden of explaining both content and return value, and it does both. It could be slightly more complete by indicating whether the spec is exhaustive over all supported directives or whether unknown directives are rejected, but for a zero-argument documentation tool it is close to sufficient.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing further the description could add on parameter meaning. It correctly avoids inventing arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it explains md2sign's markdown format and returns an example contract. The inline syntax samples ([[signature: ...]], [[field: ...]]) make the resource concrete and distinguish it from siblings like validate_markdown or render_preview, which operate on markdown rather than document the format.

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

Usage Guidelines4/5

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

Gives an explicit trigger — 'Call this first if you have not written md2sign markdown before' — which tells an agent both the ordering (first) and the condition (unfamiliarity). It stops short of naming the alternative for users who already know the format, but the conditional framing is clear and actionable.

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.