Skip to main content
Glama

Ambr

by io.github.getambr

ambr_list_templates

Read-onlyIdempotent

List available contract templates on Ambr.

Returns all active Ricardian Contract templates with their slugs, names, descriptions, categories, parameter schemas, and pricing. Use this to discover which templates are available before creating a contract with ambr_create_contract.

No authentication required.

Returns: Array of template objects with slug, name, description, category, parameter_schema, price_cents, and version fields.

Legibility: templates are the parameter schema for the dual-format contracts you create — starting here keeps your request conformant and your output defensible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the tool is free of authentication requirements and returns active templates with specific fields. This provides additional context about safety and behavior beyond annotations.

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?

The description is fairly concise with key information front-loaded. It uses three sentences: purpose, usage guidance, and output. The legibility note adds minor clutter but is not overly verbose. Could be slightly tighter, but overall effective.

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?

Given the tool has no parameters, no output schema, and annotations cover safety, the description is complete. It explains the tool's purpose, when to use it, what it returns, and that no auth is needed. This covers all essential aspects for an agent to invoke it correctly.

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 has no parameters (schema coverage 100%), so the description does not need to explain them. The baseline for 0 parameters is 4, and the description appropriately omits parameter details while otherwise adding value.

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's function: listing available contract templates on Ambr. It specifies the verb (List), resource (contract templates), and scope (available/active). It distinguishes from siblings like ambr_create_contract by stating its use for discovery before creation.

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 states when to use this tool: 'Use this to discover which templates are available before creating a contract with ambr_create_contract.' It also provides a non-usage detail (no authentication required) and clarifies the return structure, helping the agent decide when to invoke it.

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

All Ambr 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.3/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: create, retrieve, list templates, verify, and handshake are separate actions. The main confusion risk is between ambr_get_contract and ambr_get_contract_status, both take an id and return contract state, though the status tool emphasizes amendment-chain history.

Naming Consistency4/5

The ambr_ prefix and snake_case convention are applied consistently, with clear verb-like action words for most tools. ambr_agent_handshake deviates slightly from the clean verb_noun pattern, but the overall naming remains predictable.

Tool Count5/5

Six tools is a well-scoped size for a contract-management domain. Each tool covers an essential interaction: template discovery, contract creation, retrieval, status checking, hash verification, and counterparty handshake communication.

Completeness4/5

The core lifecycle is covered well: create, retrieve, check status, verify, and act on a contract. Notable gaps include no tool to list a user's own contracts or explicitly terminate one, but these can be worked around or may be intentionally handled outside the API since contracts are likely immutable.

Resources