brindley

by duckAsteroid

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

update_collection

Edit a collection README's details, including its status (active | done | abandoned).

Instructions

Edit a collection README's details, including its status (active | done | abandoned).

Input Schema

Name	Required	Description
`docs`	No	Globs of project docs this collection usually affects
`link`	No	External ticket/epic URL
`tags`	No	Tags (themes) with one-line descriptions
`agent`	No	Repo workflow agent file for this collection
`graph`	No	Dependency graph settings: direction, arrows, related, show, external, themes, enabled. null removes.
`owner`	No
`title`	No
`types`	No	Initiative types this collection uses; others are flagged
`ignore`	No	Paths or globs relative to the collection folder to ignore, e.g. ["code-review/", "completed/24-*-rationale.md"]
`status`	No
`aliases`	No	Replace the explicit aliases
`columns`	No	README table columns: { active: [...], completed: [...] }. null removes.
`folders`	No	Opt in to status folders: status → folder name, e.g. { done: done }. Status changes then move files; run tidy for existing ones. null removes (files stay where they are).
`summary`	No
`statuses`	No	This collection's own status words mapped to core statuses
`collection`	Yes	Collection name, alias or folder path
`dimensions`	No	Scoring dimensions: name → { values (first ranks first), required?, default? } or a list of values. null removes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv2.6.0Oct 13, 2026

addedInput schema / properties / aliases

Added value: +{
+  "description": "Replace the explicit aliases",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / collection / description

Previous value: -"Collection name or folder path"New value: +"Collection name, alias or folder path"

addedInput schema / properties / columns

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "README table columns: { active: [...], completed: [...] }. null removes."
+}

addedInput schema / properties / dimensions

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Scoring dimensions: name → { values (first ranks first), required?, default? } or a list of values. null removes."
+}

addedInput schema / properties / folders

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Opt in to status folders: status → folder name, e.g. { done: done }. Status changes then move files; run tidy for existing ones. null removes (files stay where they are)."
+}

addedInput schema / properties / graph

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Dependency graph settings: direction, arrows, related, show, external, themes, enabled. null removes."
+}

addedInput schema / properties / ignore

Added value: +{
+  "description": "Paths or globs relative to the collection folder to ignore, e.g. [\"code-review/\", \"completed/24-*-rationale.md\"]",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / statuses

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "This collection's own status words mapped to core statuses",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

First observedv0.1.0Oct 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations are empty, so the description carries the full behavioral burden. 'Edit' implies mutation but nothing is said about permissions, whether unlisted fields are preserved, merge-vs-replace semantics for arrays/objects, or the side effects the schema alludes to (status folders moving files). Only the implied write nature is conveyed.

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?

One tight sentence, front-loaded with the verb and resource, with zero filler. It is efficient but arguably under-specified rather than padded.

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

Completeness2/5

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

For a 17-parameter mutation tool with nested objects, no annotations and no output schema, a single sentence is not enough. Key agent-facing facts (partial updates, delete-by-null, file-moving side effects) live only in the schema and are never surfaced at the description level.

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 description coverage is 76%, so the schema already documents most of the 17 parameters, including null-removes behavior and the folder-move side effect. The description repeats the status enum that the schema already enforces and mentions no other parameter, so it adds essentially no semantic value beyond the baseline.

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+resource: editing a collection README's details, and names one editable field (status). It does not distinguish itself from the sibling 'update' or 'set_status' tools, so an agent cannot tell when this is the right entry point versus those.

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?

No when-to-use or when-not-to-use guidance. With siblings like 'update', 'set_status', and 'rename_collection' in the list, the description gives no hint about which of these a status change or rename should route through.

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

update_collection

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools