clm_bulk_update_contractsPatch metadata for up to 100 contracts with per-contract outcomes. Date changes may update scheduled emails; changes may update calendar feeds.
| Name | Required | Description | Default |
|---|---|---|---|
| updates | Yes | Version-fenced updates, <=100 |
Changes observed during successful MCP inspections.
Input schema / properties / updates / descriptionAdded value: +"Version-fenced updates, <=100"Input schema / properties / updates / items / properties / autoRenewing / descriptionPrevious value: -"Whether the fixed-term contract auto-renews"New value: +"Fixed-term auto-renewal"Input schema / properties / updates / items / properties / categoryId / anyOfRemoved value: -[
- {
- "format": "uuid",
- "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / updates / items / properties / categoryId / descriptionPrevious value: -"Contract type identifier. Set to null to clear the contract type."New value: +"Type ID; null clears"Input schema / properties / updates / items / properties / categoryId / formatAdded value: +"uuid"Input schema / properties / updates / items / properties / categoryId / typeAdded value: +[
+ "string",
+ "null"
+]Input schema / properties / updates / items / properties / endDate / anyOfRemoved value: -[
- {
- "format": "date",
- "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / updates / items / properties / endDate / formatAdded value: +"date"Input schema / properties / updates / items / properties / endDate / typeAdded value: +[
+ "string",
+ "null"
+]Input schema / properties / updates / items / properties / financialSummaryAdded value: +{
+ "maxLength": 2000,
+ "minLength": 1,
+ "type": "string"
+}Input schema / properties / updates / items / properties / financialTotalValueAdded value: +{
+ "maximum": 999999999999.99,
+ "minimum": 0,
+ "multipleOf": 0.01,
+ "type": "number"
+}Input schema / properties / updates / items / properties / financialValueCurrencyAdded value: +{
+ "maxLength": 3,
+ "minLength": 3,
+ "pattern": "^[A-Za-z]{3}$",
+ "type": "string"
+}Input schema / properties / updates / items / properties / governingLawAdded value: +{
+ "maxLength": 20000,
+ "minLength": 1,
+ "type": "string"
+}Input schema / properties / updates / items / properties / id / patternRemoved value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"Input schema / properties / updates / items / properties / isExclusiveAdded value: +{
+ "type": "boolean"
+}Input schema / properties / updates / items / properties / isOpenEnded / descriptionPrevious value: -"Whether the contract is open-ended. When true, also clears end date, auto-renewal, and renewal period."New value: +"True requires omitting endDate, autoRenewing and renewal settings."Input schema / properties / updates / items / properties / jurisdictionAdded value: +{
+ "maxLength": 20000,
+ "minLength": 1,
+ "type": "string"
+}Input schema / properties / updates / items / properties / liabilityCapAmountAdded value: +{
+ "maximum": 999999999999.99,
+ "minimum": 0,
+ "multipleOf": 0.01,
+ "type": "number"
+}Input schema / properties / updates / items / properties / liabilityCapCurrencyAdded value: +{
+ "maxLength": 3,
+ "minLength": 3,
+ "pattern": "^[A-Za-z]{3}$",
+ "type": "string"
+}Input schema / properties / updates / items / properties / liabilitySummaryAdded value: +{
+ "maxLength": 20000,
+ "minLength": 1,
+ "type": "string"
+}Input schema / properties / updates / items / properties / noticeInstructionsAdded value: +{
+ "maxLength": 20000,
+ "minLength": 1,
+ "type": "string"
+}Input schema / properties / updates / items / properties / noticePeriodUnitAdded value: +{
+ "enum": [
+ "days",
+ "weeks",
+ "months",
+ "quarters",
+ "years"
+ ],
+ "type": "string"
+}Input schema / properties / updates / items / properties / noticePeriodValueAdded value: +{
+ "exclusiveMinimum": 0,
+ "maximum": 2147483647,
+ "type": [
+ "integer",
+ "null"
+ ]
+}Input schema / properties / updates / items / properties / parties / items / properties / counterpartyId / patternRemoved value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"Input schema / properties / updates / items / properties / renewalPeriodValue / anyOfRemoved value: -[
- {
- "exclusiveMinimum": 0,
- "maximum": 2147483647,
- "type": "integer"
- },
- {
- "type": "null"
- }
-]Input schema / properties / updates / items / properties / renewalPeriodValue / exclusiveMinimumAdded value: +0Input schema / properties / updates / items / properties / renewalPeriodValue / maximumAdded value: +2147483647Input schema / properties / updates / items / properties / renewalPeriodValue / typeAdded value: +[
+ "integer",
+ "null"
+]Input schema / properties / updates / items / properties / startDate / patternRemoved value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"Input schema / properties / updates / items / properties / title / maxLengthRemoved value: -500Output schema / (root)Previous value: -{
- "$schema": "http://json-schema.org/draft-07/schema#",
- "additionalProperties": false,
- "properties": {
- "results": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "changedFields": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "error": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "errorCode": {
- "anyOf": [
- {
- "enum": [
- "conflict",
- "denied",
- "invalid",
- "not_found",
- "failed"
- ],
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "id": {
- "allOf": [
- {
- "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
- "type": "string"
- },
- {
- "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
- "type": "string"
- }
- ],
- "type": "string"
- },
- "updated": {
- "type": "boolean"
- }
- },
- "required": [
- "id",
- "updated",
- "changedFields",
- "error",
- "errorCode"
- ],
- "type": "object"
- },
- "type": "array"
- }
- },
- "required": [
- "results"
- ],
- "type": "object"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false. Beyond those, the description adds meaningful side effects: date changes can update scheduled emails and calendar feeds, and results are per-contract outcomes. It still omits conflict/version behavior and atomicity, so it is not a full 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two compact sentences are front-loaded with scope and then side effects. Every sentence adds operational context; there is no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex bulk mutation with no output schema, the description supplies the batch limit, per-contract outcomes, and notable side effects. The rich schema carries field/version details and annotations carry the safety profile, though partial-failure and atomicity semantics remain implicit.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the nested update object and required expectedUpdatedAt are documented by the schema. The description adds no parameter-level syntax or constraints beyond 'up to 100' and 'date changes'; the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with 'Patch metadata for up to 100 contracts', giving a specific verb (patch), resource (contracts), and scope (bulk up to 100). This distinguishes it from the single-contract sibling clm_update_contract even though it does not name that sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It establishes the bulk context and 100-item limit, but gives no explicit when-not guidance or named alternative such as clm_update_contract for single updates. Usage is implied by the bulk limit rather than stated as routing advice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.