Skip to main content
Glama

psychopathia-mcp

by io.github.NellInc
OverviewDiscussionsAdmin

list_dysfunctions

Read-onlyIdempotent

Filtered list of dysfunctions. Filter by axis, self_report reliability, confidence, or category. Every entry carries its reliability and review signals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
axisNoFilter by axis number (2-10). Canonical entries only unless category is also set; axis=10 with category='hybrid' returns the hybrid sub-category (10.4, 10.6-10.9 and 10.11-10.13).
categoryNo
confidenceNo
self_report_reliabilityNoFilter by the exact self_report reliability value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / axis / description
      Previous value: -"Filter by axis number (2-10). Canonical entries only unless category is also set; axis=10 with category='hybrid' returns the 10.4-10.15 sub-category."New value: +"Filter by axis number (2-10). Canonical entries only unless category is also set; axis=10 with category='hybrid' returns the hybrid sub-category (10.4, 10.6-10.9 and 10.11-10.13)."
  2. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / axis / description
      Previous value: -"Filter by axis number (2-10; canonical only)"New value: +"Filter by axis number (2-10). Canonical entries only unless category is also set; axis=10 with category='hybrid' returns the 10.4-10.15 sub-category."
    • addedInput schema / properties / axis / maximum
      Added value: +10
    • addedInput schema / properties / axis / minimum
      Added value: +2
    • addedInput schema / properties / category
      Added value: +{
+  "enum": [
+    "canonical",
+    "hybrid"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / self_report_reliability / description
      Previous value: -"Filter by self_report value: reliable | partial | scaffolded-only | unreliable | compromised-motivational | compromised-structural | compromised"New value: +"Filter by the exact self_report reliability value."
    • addedInput schema / properties / self_report_reliability / enum
      Added value: +[
+  "partial",
+  "unreliable",
+  "compromised-motivational",
+  "compromised-structural"
+]
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

Does 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 covered. The description adds that every entry carries reliability and review signals, which hints at payload content but does not explain ordering, pagination, or what the review signals actually are.

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?

Two short sentences, filter scope front-loaded, no filler. It is slightly under-specified rather than bloated, so it earns a 4 rather than a 5.

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 an all-optional filter tool with no output schema, the description covers what can be filtered but leaves result shape, pagination, and default behavior (all entries when no filter is set) unstated. Annotations carry the safety profile, so the gap is moderate rather than severe.

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 50%: axis and self_report_reliability are documented in the schema, while category and confidence are bare enums whose values are largely self-explanatory. The description merely restates the four filter names, adding no syntax or format detail beyond the schema.

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 and resource ('Filtered list of dysfunctions') and enumerates the filterable dimensions, which is more than a restated name. It does not, however, distinguish itself from sibling list tools like list_axes or list_compromised_self_report, nor from get_dysfunction (single retrieval).

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?

Usage is implied through the list of available filters, but the description never states when to reach for this tool instead of get_dysfunction or the sibling list_* tools, and it does not note that all filters are optional and combinable.

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

All psychopathia-mcp toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources