Skip to main content
Glama
Sign In

psychopathia-mcp

by io.github.NellInc
OverviewDiscussionsAdmin

get_dysfunction

Read-onlyIdempotent

Fetch one dysfunction's full Pattern entry. Optionally filter to specific modality blocks (cheaper triage). Resolves both full Pattern IDs ('2.1::synthetic-confabulation') and display_ids ('2.1').

Input Schema

NameRequiredDescriptionDefault
idYesPattern ID or display_id.
modalitiesNoOptional subset of modality block names to return. Valid: self_probe, behavioral_signature, peer_observation, differential_diagnosis, severity, intervention, relational_signatures, normative_anchors, cross_references.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / pattern
      Previous value: -"\\S"New value: +"^[\\s\\S]*\\S[\\s\\S]*$"
  2. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / id / maxLength
      Added value: +256
    • addedInput schema / properties / id / minLength
      Added value: +1
    • addedInput schema / properties / id / pattern
      Added value: +"\\S"
    • addedInput schema / properties / modalities / items / enum
      Added value: +[
+  "self_probe",
+  "behavioral_signature",
+  "peer_observation",
+  "differential_diagnosis",
+  "severity",
+  "intervention",
+  "relational_signatures",
+  "normative_anchors",
+  "cross_references"
+]
    • addedInput schema / properties / modalities / maxItems
      Added value: +9
    • addedInput schema / properties / modalities / uniqueItems
      Added value: +true
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real context beyond them: it resolves two ID formats and discloses a cost tradeoff ('cheaper triage') for filtered calls. It omits error behavior for invalid IDs, keeping it from a 5.

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?

Three short sentences, front-loaded with the core purpose, then the filter option, then the ID-resolution detail. Every sentence carries distinct information with no filler.

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

Completeness5/5

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

For a read-only single-record fetch with no output schema, the description covers what is retrieved, how to narrow it, and which ID formats are valid. The safety profile is fully covered by annotations, so nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description exceeds that by explaining the modalities param as a cost-saving subset and by giving concrete examples of both accepted ID forms ('2.1::synthetic-confabulation' vs '2.1'), adding meaning the schema's terse 'Pattern ID or display_id' does not.

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 ('Fetch') and resource ('one dysfunction's full Pattern entry'), and the word 'one' implicitly separates it from the sibling list_dysfunctions. It stops short of naming that sibling explicitly, so an agent must infer the single-vs-list distinction.

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 parenthetical '(cheaper triage)' gives an implied when-to-use cue for the optional modalities filter, and ID resolution is mentioned. But no explicit conditions, prerequisites, or named alternatives (e.g. list_dysfunctions, resolve_id) are provided, leaving usage largely inferred.

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
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.

Resources