clm_read_contract_documentRead accessible document text in cited sections; cursor continues remaining text.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID | |
| limit | No | Maximum text length | |
| cursor | No | Prior read cursor | |
| documentId | No | Effective primary or related document ID |
Changes observed during successful MCP inspections.
Input schema / properties / cursor / descriptionPrevious value: -"Continuation cursor from a prior read"New value: +"Prior read cursor"Input schema / properties / documentId / descriptionPrevious value: -"Optional effective primary or related document identifier"New value: +"Effective primary or related document ID"Input schema / properties / documentId / 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 / id / descriptionPrevious value: -"Contract identifier"New value: +"ID"Input schema / 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 / limit / descriptionPrevious value: -"Maximum document text to return"New value: +"Maximum text length"Output schema / (root)Previous value: -{
- "$schema": "http://json-schema.org/draft-07/schema#",
- "additionalProperties": false,
- "properties": {
- "completeness": {
- "enum": [
- "complete",
- "partial"
- ],
- "type": "string"
- },
- "items": {
- "description": "Document text with citations",
- "items": {
- "additionalProperties": false,
- "properties": {
- "citation": {
- "additionalProperties": false,
- "description": "Source citation for this text",
- "properties": {
- "chunkId": {
- "anyOf": [
- {
- "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"
- },
- {
- "type": "null"
- }
- ]
- },
- "citationId": {
- "description": "Stable evidence citation identifier",
- "minLength": 1,
- "type": "string"
- },
- "contractId": {
- "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"
- }
- ],
- "description": "Contract UUID containing the cited passage",
- "type": "string"
- },
- "contractTitle": {
- "description": "Contract title at the cited passage",
- "minLength": 1,
- "type": "string"
- },
- "endOffset": {
- "anyOf": [
- {
- "maximum": 9007199254740991,
- "minimum": 0,
- "type": "integer"
- },
- {
- "type": "null"
- }
- ]
- },
- "fileId": {
- "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"
- }
- ],
- "description": "Effective document version UUID containing the passage",
- "type": "string"
- },
- "fileName": {
- "description": "Document file name",
- "minLength": 1,
- "type": "string"
- },
- "fileRole": {
- "enum": [
- "primary",
- "related"
- ],
- "type": "string"
- },
- "fileStatus": {
- "const": "effective",
- "type": "string"
- },
- "startOffset": {
- "anyOf": [
- {
- "maximum": 9007199254740991,
- "minimum": 0,
- "type": "integer"
- },
- {
- "type": "null"
- }
- ]
- }
- },
- "required": [
- "citationId",
- "contractId",
- "contractTitle",
- "fileId",
- "chunkId",
- "fileName",
- "fileRole",
- "fileStatus",
- "startOffset",
- "endOffset"
- ],
- "type": "object"
- },
- "content": {
- "description": "Matched or sequential document text",
- "type": "string"
- },
- "context": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- }
- },
- "required": [
- "content",
- "citation"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "nextCursor": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "status": {
- "enum": [
- "ok",
- "missing",
- "ambiguous",
- "processing",
- "unindexed",
- "no_match",
- "exhausted",
- "invalid_cursor"
- ],
- "type": "string"
- }
- },
- "required": [
- "status",
- "completeness",
- "items",
- "nextCursor"
- ],
- "type": "object"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds genuine context beyond that: results are access-scoped ('accessible'), text comes back in cited sections, and the cursor continues the remaining text. It does not say what happens on an invalid or expired cursor, or whether text is truncated per section.
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?
A single compact sentence with no filler, and the pagination behavior is placed last where an agent will look for it after learning the core purpose. It is slightly telegraphic – 'cited sections' is unexplained – but nothing is wasted.
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 four-parameter read tool with no output schema, the description covers the core purpose and the pagination loop, which is the main thing an agent must get right. Gaps remain around the two competing ID parameters and the shape of 'cited sections' in the response, which the absent output schema leaves undocumented.
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 description coverage is 100%, so the baseline is 3. The description earns its keep by explaining cursor semantics ('continues remaining text'), but it does not clarify the potentially confusing distinction between 'id' (required) and 'documentId' (effective primary or related document), nor what 'limit' bounds in practice.
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 names a specific verb and resource (read document text) and scopes it to 'accessible' documents returned in 'cited sections'. That is clear enough to distinguish it from a download-URL tool, though it never names the closest sibling (clm_get_contract_document_download_url) or the search tool explicitly.
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?
There is no when-to-use or when-not-to-use guidance, and no alternative is named despite several siblings that could plausibly be confused with it (download URL, search documents, get contract). The word 'accessible' implies an access precondition but does not state how to check or satisfy it.
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.