Skip to main content
Glama
Sign In
Liminate Authoring MCP

Liminate Authoring MCP

by rmichaelthomas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

draft_agreement

Assembles a Liminate Agreement from structured rules (verb/condition/reason/unless/starting/until) or returns a vendored template. Validates the draft against the interpreter before returning.

Instructions

Assemble a Liminate Agreement from structured rules (verb/condition/ reason/unless/starting/until), or return a vendored template by template_id. Always validates the drafted source against the interpreter before returning — never claims a draft is valid without confirming it.

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

Input Schema

NameRequiredDescriptionDefault
aboutNo
rulesNo
template_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the critical validation behavior (always validates, never claims validity without confirmation) and the structured rule format. While it doesn't mention error handling or permissions, the core behavioral traits are well communicated.

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?

Two sentences, no redundancy. The description is front-loaded with the primary action and includes a critical behavioral guarantee. Every word adds value.

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?

Given the optional parameters, no output schema, and no annotations, the description covers the tool's functionality and safety guarantee. It could optionally mention the output format or errors, but it is adequate for an agent to understand its use.

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 0%, but the description adds meaning: it specifies that 'rules' is an array of objects with fields verb/condition/reason/unless/starting/until, and that 'template_id' returns a vendored template. The 'about' parameter remains undefined but is optional; overall, the description compensates significantly for the schema's lack of detail.

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?

The description clearly states the tool assembles a Liminate Agreement from structured rules or returns a vendored template, with validation guarantee. This action verb and resource are specific and distinguish from sibling tools like validate_agreement or explain_clause.

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?

The description implies use cases (drafting from rules or template), but lacks explicit guidance on when to use this tool versus alternatives like validate_agreement or test_agreement. No when-not or exclusion criteria are provided.

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

Deploy Server

Other Tools