List parties
clm_list_partiesRead-onlyIdempotent
List workspace company/person contract parties.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Type filter | |
| query | No | Literal case-insensitive substring in display/legal name |
Contracko
Schema Changelog
Changes observed during successful MCP inspections.
Changed3 schema fields changed
- changed
Input schema / properties / query / descriptionPrevious value: -"Literal case-insensitive substring in a party display or legal name."New value: +"Literal case-insensitive substring in display/legal name" - changed
Input schema / properties / type / descriptionPrevious value: -"Return only this party type."New value: +"Type filter" - changed
Output schema / (root)Previous value: -{ - "$schema": "http://json-schema.org/draft-07/schema#", - "additionalProperties": false, - "properties": { - "items": { - "description": "Parties in this workspace", - "items": { - "additionalProperties": false, - "properties": { - "address": { - "anyOf": [ - { - "anyOf": [ - { - "anyOf": [ - { - "type": "string" - }, - { - "type": "number" - }, - { - "type": "boolean" - }, - { - "type": "null" - } - ] - }, - { - "additionalProperties": {}, - "propertyNames": { - "type": "string" - }, - "type": "object" - }, - { - "items": {}, - "type": "array" - } - ] - }, - { - "type": "null" - } - ] - }, - "contactDisplayName": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "contactEmail": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "contactName": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "contactPhone": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "contactRole": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "createdAt": { - "format": "date-time", - "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])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$", - "type": "string" - }, - "email": { - "anyOf": [ - { - "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" - }, - "isOwned": { - "type": "boolean" - }, - "legalName": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "name": { - "type": "string" - }, - "notes": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "organisationId": { - "type": "string" - }, - "phone": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "registrationNumber": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "tags": { - "items": { - "type": "string" - }, - "type": "array" - }, - "taxId": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "type": { - "enum": [ - "individual", - "company", - "non-profit", - "government" - ], - "type": "string" - }, - "updatedAt": { - "format": "date-time", - "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])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$", - "type": "string" - }, - "website": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "required": [ - "id", - "organisationId", - "type", - "isOwned", - "name", - "legalName", - "email", - "phone", - "website", - "contactName", - "contactDisplayName", - "contactRole", - "contactEmail", - "contactPhone", - "address", - "taxId", - "registrationNumber", - "tags", - "notes", - "createdAt", - "updatedAt" - ], - "type": "object" - }, - "type": "array" - } - }, - "required": [ - "items" - ], - "type": "object" -}New value: +null
- First observed
TDQS
B3.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety and side-effect behavior are covered structurally. The description's only added behavioral fact is that results are workspace-scoped, which is useful but thin; nothing is said about result ordering, pagination, or result limits. No annotation contradiction.
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?
A single short sentence with no filler, and the resource and scope are front-loaded. It is efficient, though its brevity comes at the cost of the missing usage and return-shape context rather than being a model of tight structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-optional-parameter read tool with no output schema and rich read-only annotations, the description is close to adequate but leaves one material gap: whether it returns all workspace parties or only those tied to contracts, which is exactly what determines the choice against clm_get_party and the create/update siblings. Pagination behavior is also unaddressed.
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%, with both 'type' and 'query' fully documented including the enum and the case-insensitive substring matching rule, so the baseline of 3 applies. The description adds essentially nothing beyond the schema, and the phrase 'company/person' is less precise than the enum's four values.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (contract parties) with the scope qualifier 'workspace', so an agent can tell it is the collection read rather than the single-record clm_get_party or the write-side clm_create_party. The 'company/person' fragment hints at party kinds but is never reconciled with the 'type' enum, so the resource is clear while the scope of what is returned stays slightly fuzzy.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no statement of when to prefer this over clm_get_party, and no note that it is workspace-wide rather than scoped to a specific contract. The agent must infer the choice entirely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.