Coordination Memory MCP

by yanqiw

Overview Schema Source Related Servers Discussions Admin

Python

Local

list_contracts

Retrieve compact contracts for a specific team by providing its team ID. Discover team IDs with get_workspace_detail.

Instructions

List compact contracts for one exact team ID.

Discover team IDs with get_workspace_detail.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`team_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.2.8Sep 20, 2026

removedInput schema / properties / team_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / team_id / default
```
Removed value: -null
```
addedInput schema / properties / team_id / type
```
Added value: +"string"
```

removedInput schema / properties / workspace_id

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Workspace Id"
-}

addedInput schema / required
```
Added value: +[
+  "team_id"
+]
```
addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "title": "Result",
-    "type": "array"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

changedOutput schema / title

Previous value: -"list_contractsOutput"New value: +"list_contractsDictOutput"

First observedv0.2.6Sep 6, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. 'Compact contracts' and 'one exact team ID' add useful behavioral context, but the description does not state whether the operation is read-only, how results are ordered, or whether pagination applies. The output schema mitigates return-format concerns.

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 sentences with no wasted words. The main purpose is front-loaded, and the discovery pointer is placed as a natural follow-up, making the description easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple one-parameter listing tool, and the description covers scope and ID discovery. An output schema is present to explain return values, so the main missing piece is only a more explicit behavioral note about ordering or empty results.

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?

The schema only provides team_id as a string with no description, so the tool description must add meaning. It does by specifying that the ID must be exact and by pointing to get_workspace_detail for discovery. For a single parameter, this is sufficient practical guidance.

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?

The description clearly states the action ('List'), the resource ('contracts'), and the scope ('one exact team ID'), so an agent can tell what the tool does. It does not explicitly name a sibling like get_contract_detail, but the 'compact' qualifier hints at a summary list rather than full details.

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 gives a useful prerequisite: discover team IDs with get_workspace_detail, and it constrains usage to an exact team ID. It does not explicitly state when to prefer this over list_workspaces or get_contract_detail, so it stops short of full alternative routing.

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