Skip to main content
Glama

Validate a contract

validate_markdown
Read-onlyIdempotent

Check that markdown has correctly formed signature fields before you draft or send it. Returns detected recipients, title, style, envelopes_required (always 1), the SHA-256 document hash, and errors/warnings with line numbers. Free, no account needed.

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

Input Schema

NameRequiredDescriptionDefault
markdownYesThe full markdown contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds auth/cost context ('Free, no account needed') plus the constant envelopes_required=1. It could say more about what counts as an error versus a warning, but the safety profile is well covered.

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 short sentences, front-loaded with the purpose and the sequencing condition, then the return contents and the cost/auth note. Every sentence carries information an agent needs.

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 output schema, listing the returned fields (recipients, title, style, envelopes_required, hash, errors/warnings with line numbers) meaningfully fills the gap. It does not point to get_markdown_spec for the field syntax the agent would need to fix reported errors, which is the one notable omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter with 100% schema coverage, so the baseline is 3. The description implies the markdown must contain well-formed signature fields but adds no syntax or format detail beyond the schema.

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 specific verb and resource ('Check that markdown has correctly formed signature fields') and scopes it to a pre-draft/pre-send moment. It is clearly a read-only validator rather than a drafting or sending tool, though it does not name a specific sibling to contrast with.

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?

'Before you draft or send it' gives an explicit trigger condition that routes the agent between this tool and create_draft/send_document. No explicit exclusions or when-not-to-use guidance is given, so it stops short of a 5.

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.