viridis-agent-fleet

Overview Schema Source Related Servers Discussions Admin

wavefunction__register_collective

[wavefunction — demand-side agent/collective discovery] Register an agent/collective into the match index (mission + domain profile + constitutional alignment scores + capacity).

Instructions

[wavefunction — demand-side agent/collective discovery] Register an agent/collective into the match index (mission + domain profile + constitutional alignment scores + capacity).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`mission`	Yes
`capacity`	No
`collective_id`	Yes
`domain_profile`	No
`constitutional_scores`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.13Sep 13, 2026
Removedv0.1.12Jul 28, 2026
Changed13 schema fields changedv0.1.11Jul 18, 2026
- addedInput schema / properties / capacity / title
```
Added value: +"Capacity"
```
- addedInput schema / properties / collective_id / title
```
Added value: +"Collective Id"
```
- addedInput schema / properties / constitutional_scores / anyOf
```
Added value: +[
+  {
+    "additionalProperties": {
+      "type": "number"
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / constitutional_scores / default
```
Added value: +null
```
- addedInput schema / properties / constitutional_scores / title
```
Added value: +"Constitutional Scores"
```
- removedInput schema / properties / constitutional_scores / type
```
Removed value: -"object"
```
- addedInput schema / properties / domain_profile / anyOf
```
Added value: +[
+  {
+    "additionalProperties": {
+      "type": "number"
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / domain_profile / default
```
Added value: +null
```
- addedInput schema / properties / domain_profile / title
```
Added value: +"Domain Profile"
```
- removedInput schema / properties / domain_profile / type
```
Removed value: -"object"
```
- addedInput schema / properties / mission / title
```
Added value: +"Mission"
```
- addedInput schema / properties / name / title
```
Added value: +"Name"
```
- addedInput schema / title
```
Added value: +"register_collectiveArguments"
```
Changed13 schema fields changedv0.1.9Jul 16, 2026
- removedInput schema / properties / capacity / title
```
Removed value: -"Capacity"
```
- removedInput schema / properties / collective_id / title
```
Removed value: -"Collective Id"
```
- removedInput schema / properties / constitutional_scores / anyOf
```
Removed value: -[
-  {
-    "additionalProperties": {
-      "type": "number"
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / constitutional_scores / default
```
Removed value: -null
```
- removedInput schema / properties / constitutional_scores / title
```
Removed value: -"Constitutional Scores"
```
- addedInput schema / properties / constitutional_scores / type
```
Added value: +"object"
```
- removedInput schema / properties / domain_profile / anyOf
```
Removed value: -[
-  {
-    "additionalProperties": {
-      "type": "number"
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / domain_profile / default
```
Removed value: -null
```
- removedInput schema / properties / domain_profile / title
```
Removed value: -"Domain Profile"
```
- addedInput schema / properties / domain_profile / type
```
Added value: +"object"
```
- removedInput schema / properties / mission / title
```
Removed value: -"Mission"
```
- removedInput schema / properties / name / title
```
Removed value: -"Name"
```
- removedInput schema / title
```
Removed value: -"register_collectiveArguments"
```
Changed13 schema fields changedJul 13, 2026
- addedInput schema / properties / capacity / title
```
Added value: +"Capacity"
```
- addedInput schema / properties / collective_id / title
```
Added value: +"Collective Id"
```
- addedInput schema / properties / constitutional_scores / anyOf
```
Added value: +[
+  {
+    "additionalProperties": {
+      "type": "number"
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / constitutional_scores / default
```
Added value: +null
```
- addedInput schema / properties / constitutional_scores / title
```
Added value: +"Constitutional Scores"
```
- removedInput schema / properties / constitutional_scores / type
```
Removed value: -"object"
```
- addedInput schema / properties / domain_profile / anyOf
```
Added value: +[
+  {
+    "additionalProperties": {
+      "type": "number"
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / domain_profile / default
```
Added value: +null
```
- addedInput schema / properties / domain_profile / title
```
Added value: +"Domain Profile"
```
- removedInput schema / properties / domain_profile / type
```
Removed value: -"object"
```
- addedInput schema / properties / mission / title
```
Added value: +"Mission"
```
- addedInput schema / properties / name / title
```
Added value: +"Name"
```
- addedInput schema / title
```
Added value: +"register_collectiveArguments"
```
Changed13 schema fields changedJul 13, 2026
- removedInput schema / properties / capacity / title
```
Removed value: -"Capacity"
```
- removedInput schema / properties / collective_id / title
```
Removed value: -"Collective Id"
```
- removedInput schema / properties / constitutional_scores / anyOf
```
Removed value: -[
-  {
-    "additionalProperties": {
-      "type": "number"
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / constitutional_scores / default
```
Removed value: -null
```
- removedInput schema / properties / constitutional_scores / title
```
Removed value: -"Constitutional Scores"
```
- addedInput schema / properties / constitutional_scores / type
```
Added value: +"object"
```
- removedInput schema / properties / domain_profile / anyOf
```
Removed value: -[
-  {
-    "additionalProperties": {
-      "type": "number"
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / domain_profile / default
```
Removed value: -null
```
- removedInput schema / properties / domain_profile / title
```
Removed value: -"Domain Profile"
```
- addedInput schema / properties / domain_profile / type
```
Added value: +"object"
```
- removedInput schema / properties / mission / title
```
Removed value: -"Mission"
```
- removedInput schema / properties / name / title
```
Removed value: -"Name"
```
- removedInput schema / title
```
Removed value: -"register_collectiveArguments"
```
First observedJul 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. While it names fields, it doesn't clarify whether the tool is idempotent, requires specific permissions, or what happens on duplicate collective_id. The mutation nature is implied but not elaborated.

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?

The description is a single sentence with a bracketed prefix that adds context but is somewhat redundant. It front-loads the purpose and lists key fields compactly, but the prefix could be integrated. Overall, it's efficient.

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?

With 6 parameters (3 required), no output schema, and no annotations, the description leaves many gaps: return value, side effects, idempotency, required permissions, and how the fields interact. A registration tool of this complexity should provide more context for accurate use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should explain parameter meanings beyond their names. It mentions mission, domain profile, constitutional scores, and capacity, but does not describe their expected formats, constraints, or relationships. For example, domain_profile is an object with number values, but no hint is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('register') and resource ('agent/collective into the match index'), listing key fields (mission, domain profile, constitutional alignment scores, capacity). It distinguishes itself from sibling tools like wavefunction__intake and wavefunction__collapse by focusing on registration into a match index.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for registration but provides no explicit guidance on when to use this tool vs alternatives like wavefunction__intake or wavefunction__collapse. No when-not-to-use or prerequisites mentioned.

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

Deploy Server

wavefunction__register_collective

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools