Skip to main content
Glama
Sign In
Liminate Authoring MCP

Liminate Authoring MCP

by rmichaelthomas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

explain_clause

Explains any clause from a Liminate Agreement in plain English, detailing verb, condition, rationale, temporal window, and exceptions.

Instructions

Explain each clause of a Liminate Agreement in plain English: verb, condition, rationale, temporal window (active/expired/future/unbounded), and any unless-exception.

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": {
      "source": "<source>"
    },
    "name": "explain_clause"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations provided; description only states it explains without disclosing behavioral traits like read-only, authentication needs, or side effects. Major gap given annotation absence.

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?

One sentence, concise and front-loaded with main action. However, lacks necessary detail, making it efficient but incomplete.

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

Completeness2/5

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

No output schema or return format described; parameter semantics missing; description incomplete for agent to reliably invoke despite simple tool.

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

Parameters1/5

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

Single parameter 'source' has no description in schema (0% coverage) and tool description does not define its meaning or format, leaving agent unsure what to provide.

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?

Description clearly states it explains clauses of a Liminate Agreement in plain English, listing specific aspects covered (verb, condition, rationale, temporal window, unless-exception). This distinguishes it from sibling tools like draft_agreement or validate_agreement.

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?

Implicitly suggests use when clause explanation is needed, but no explicit guidance on when not to use or comparison with alternatives. Lack of when-not or alternative references reduces clarity.

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