Ambr

ambr_get_contract_status

Read-onlyIdempotent

Check the status of a contract and its amendment chain.

Returns the current status and any linked amendments (parent or child contracts). Useful for verifying if a contract is active, amended, or terminated.

Args:

id (string, required): Contract ID, SHA-256 hash, or UUID

Returns:

contract_id, status, created_at
amendment_type, parent_contract_hash
amendments: Array of child contracts (if any)

Legibility: amendments are bilateral and themselves dual-format — the chain stays legible from original through every revision.

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": {
      "id": "<id>"
    },
    "name": "ambr_get_contract_status"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Contract ID (amb-YYYY-NNNN), SHA-256 hash, or UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral details about the amendment chain's legibility and return format, providing value beyond annotations. No contradictions.

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?

Description is front-loaded with purpose, followed by usage, arguments, returns, and legibility note. The Args section redundantly restates schema info, slightly reducing conciseness, but overall well-structured.

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?

Despite lacking an output schema, the description lists return fields and explains the tool's role in contract status verification. For a simple, single-parameter read-only tool, this is fully adequate.

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 coverage is 100% and both schema and description define the 'id' parameter identically. The description adds no new semantics beyond what the schema already provides, meeting baseline only.

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 verb ('Check') and resource ('status of a contract and its amendment chain'), and distinguishes from siblings like ambr_get_contract by focusing on status and amendments.

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

Usage Guidelines4/5

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

The description explains when to use ('verifying if a contract is active, amended, or terminated') and implies alternatives by contrast with sibling tools, though explicit when-not-to-use is missing.

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

All Ambr tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?