Skip to main content
Glama

Open Agreements

by io.github.open-agreements

list_templates

Read-only

List all available legal agreement templates as a paginated compact catalog. Returns lightweight metadata for discovery — call get_template for full per-field detail. Templates are returned in stable lexicographic order by template_id. For finding templates by topic, jurisdiction, or source, use search_templates instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size (default 25, max 100).
cursorNoOpaque pagination cursor returned by a prior call. Omit on the first page.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque pagination cursor returned by a prior call. Omit on the first page.",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Page size (default 25, max 100).",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / mode
      Removed value: -{
-  "description": "Response detail mode. Defaults to \"compact\".",
-  "enum": [
-    "compact",
-    "full"
-  ],
-  "type": "string"
-}
  2. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"Response detail mode. Defaults to \"full\"."New value: +"Response detail mode. Defaults to \"compact\"."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true and destructiveHint=false; description adds that results are paginated, compact/lightweight metadata, and in stable lexicographic order by template_id. It does not describe return fields, but that's acceptable given the 'call get_template' pointer.

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, first sentence immediately states purpose; no filler or redundancy. Every sentence adds distinct information (scope, guidance, ordering/alternative).

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

Completeness5/5

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

For a low-complexity read-only list tool with full schema coverage and a pointer to get_template for detail, the description covers usage and behavior adequately. The absence of an output schema is mitigated by the explicit statement that it returns lightweight metadata for discovery.

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?

Schema covers 100% of parameters with descriptions for limit and cursor, so the description adds little beyond mentioning pagination. Baseline 3 applies because schema does the heavy lifting.

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 opens with 'List all available legal agreement templates as a paginated compact catalog' — a specific verb and resource. It distinguishes from siblings by noting get_template for full detail and search_templates for topic-based discovery.

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

Usage Guidelines5/5

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

Explicitly says 'call get_template for full per-field detail' and 'use search_templates instead' for topic/jurisdiction/source searches. This clearly delineates when to use this tool versus alternatives.

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

All Open Agreements toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clear and distinct purpose: template browsing (list_templates, search_templates, get_template), template filling (fill_template), signature workflow (send_for_signature, check_signature_status). No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_templates, check_signature_status). Verbs and nouns are clearly chosen, making the pattern predictable.

Tool Count5/5

With 6 tools covering the core workflow of template discovery, filling, and e-signature, the count is well-scoped and appropriate for the server's purpose. No unnecessary tools and no critical missing functionality.

Completeness5/5

The tool set covers the full lifecycle of working with legal agreement templates: discover (list, search, get), create filled document (fill_template), send for signature (send_for_signature), and retrieve signed PDF (check_signature_status). No obvious gaps for the intended use case.

Resources