Skip to main content
Glama

list_contract_templates

Read-onlyIdempotent

Lists three free local contract template presets so agents can inspect supported CSV validation profiles before preparing or accepting a contract.

Instructions

FREE local catalog of three explicit supported-profile presets. No token, state, model call, acceptance, or purchase.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
templatesYes
catalogVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new operational context beyond that: the catalog is free and local, requires no token or auth, makes no model call, and has no acceptance/purchase side effects — all useful for an agent deciding whether it can call this cheaply and safely.

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?

Two tight sentences with the most decision-relevant fact (FREE, local) front-loaded, followed by an exclusion list. "Supported-profile presets" is somewhat jargon-heavy, but nothing is redundant or padded.

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

Completeness3/5

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

A zero-parameter, no-auth read tool with an output schema is a low-complexity case, and the description covers cost, locality, and side-effect absence. What it omits is what a "supported-profile preset" actually is and how the returned presets feed into sibling tools like prepare_contract_draft, leaving a semantic gap an agent must guess at.

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 and the schema confirms an empty properties object, so there is no parameter meaning to convey. Baseline 4 applies; the description correctly makes no parameter claims that could mislead.

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?

The description identifies the resource as a "catalog" of "three explicit supported-profile presets," which combined with the name makes clear it returns a fixed list of preset contract templates. It stops short of naming a sibling, so the agent must infer that get_contract_template fetches a single one rather than the list.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no comparison to alternatives such as get_contract_template or prepare_contract_draft. The "No token, state, model call, acceptance, or purchase" clause hints at what the tool does not do, but it never states the condition under which an agent should call it (e.g., before preparing a draft).

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