shiply

Create an amendment to a signed contract

contract_amend

Create an amendment to a SIGNED parent contract. Scope delta required; fee delta and target date optional. Returns the draft amendment for editing before send — call contract_send with the returned amendment id to fire it. Cannot amend an amendment (amend the parent instead).

Input Schema

TableJSON Schema

Name	Required	Description
`scopeDelta`	Yes	What's changing — visible to customer.
`feeDeltaCents`	No	Optional fee adjustment in cents. Can be negative for descope.
`parentContractId`	Yes	id of the SIGNED parent contract to amend
`targetCompletionDate`	No	Optional ISO date (YYYY-MM-DD) for revised completion.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJun 23, 2026

addedInput schema / properties / parentContractId / description
```
Added value: +"id of the SIGNED parent contract to amend"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {}
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedJun 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Discloses that the tool creates a draft amendment (non-destructive creation) and requires a signed parent contract. The idempotentHint=false annotation is honored; the description adds context about the two-step process and state requirement.

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?

Two concise sentences with no fluff. Front-loaded with core purpose, followed by workflow and constraint. Every sentence adds value.

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 presence of an output schema and full parameter descriptions, the description adequately covers the creation workflow, state prerequisites, and integration with contract_send. No gaps for agent decision-making.

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?

Schema already covers all parameters (100% coverage), but the description adds workflow context (e.g., 'scope delta required; fee delta and target date optional') and constraint ('negative for descope' reinforces schema). Minor extra value beyond schema.

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 'Create' and the resource 'amendment to a SIGNED parent contract'. It distinguishes from siblings like contract_draft and contract_send by specifying the workflow and constraints (e.g., cannot amend an amendment).

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?

Provides explicit when-to-use (create amendment to signed parent) and when-not (cannot amend an amendment). Also guides next steps ('call contract_send with the returned amendment id to fire it') and clarifies required/optional parameters.

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

All shiply tools Inspect

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.

Resources

Need Help?