Skip to main content
Glama

mindpulse

Get evidence-based mental health guidance, therapy platform matching, and crisis resource routing. Covers assessment, burnout, sleep disorders, and more.

Instructions

MindPulse: Global mental health intelligence API. Evidence-based guidance on therapy platform matching, mental health assessment, burnout, psychiatric medication context, coping techniques, sleep disorders (CBT-

Coverage: Global

Endpoints: • match ($0.10): Therapy platform matching • assessment ($0.10): Mental health self-assessment • burnout ($0.10): Burnout assessment and recovery protocol • medication ($0.10): Psychiatric medication context • technique ($0.10): Evidence-based coping technique guide • sleep ($0.10): Sleep disorder guidance (CBT-I protocol) • grief ($0.10): Grief and loss support • relationship ($0.10): Relationship and communication guidance • workplace ($0.10): Workplace mental health guidance • crisis ($0.10): Crisis resource routing — ALWAYS FREE

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: match | assessment | burnout | medication | technique | sleep | grief | relationship | workplace | crisis
langNoResponse language (e.g., es, fr, de, ja)
concernsNoMental health concerns (e.g., depression,anxiety,trauma)
budgetNoMonthly budget in USD (e.g., 60, 100, 200)
modalityNoPreferred therapy modality (CBT, DBT, ACT, coaching)
insuranceNoInsurance carrier or 'self-pay'
durationNoHow long symptoms have been present (e.g., 3+months)
impactNoHow symptoms impact daily function (mild/moderate/severe)
situationNoDescribe the burnout situation (e.g., 5+years+ICU+nursing)
roleNoJob role or profession
drugNoMedication name (generic or brand — e.g., sertraline, Zoloft, quetiapine)
conditionNoCondition it is prescribed for
concernNoMental health concern to address (e.g., panic+attacks, rumination, anger)
approach_preferenceNoPreferred approach type (CBT, DBT, ACT, mindfulness, somatic)
severityNoSeverity description (e.g., unable+to+fall+asleep, waking+frequently)
time_since_lossNoTime since the loss (e.g., 2+weeks, 3+months)
typeNoType of loss (spousal, parent, child, pet, relationship, identity, health)
relationship_typeNoType of relationship (romantic, family, friendship, work)
jurisdictionNoCountry/jurisdiction for legal framework (US, UK, CA, AU)
countryNoUser's country for localized crisis resources
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose pricing per endpoint (e.g., '$0.10' for most) and notes that crisis routing is 'ALWAYS FREE', which adds useful transparency. However, it lacks details on authentication requirements, rate limits, destruction risk, or what happens on error. The pricing information is a positive but insufficient for full transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description begins with a clear title and line listing endpoints, which is well-structured. However, it is somewhat verbose—each endpoint is repeated with its cost, and the list could be condensed. The description front-loads the purpose but contains redundant elements, making it less concise than ideal.

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?

Given the tool's complexity (20 parameters, multiple actions, no output schema), the description is incomplete. It lists endpoints but does not explain which parameters are relevant for each action, nor does it provide examples or expected return formats. An agent would struggle to correctly invoke this tool without additional guidance on parameter-action mapping.

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 100%—every parameter already has a description in the input schema. The tool description adds no additional semantic meaning beyond the schema; it merely lists endpoint names and costs. Per the rubric, with high schema coverage, the baseline is 3, and the description does not exceed that.

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 identifies the tool as a 'Global mental health intelligence API' and lists specific endpoints (match, assessment, burnout, etc.), establishing a clear verb+resource relationship. However, it does not distinguish this tool from its many sibling pulse tools (e.g., careerpulse, chronicapulse), which also serve specialized domains. The purpose is clear but lacks sibling differentiation.

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?

The description provides no explicit guidance on when to use this tool versus alternative tools. While the context of 'mental health intelligence' implies its domain, there is no mention of when not to use it, prerequisites, or how to choose among the many sibling pulse tools. This omission leaves the agent without decision support for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/pulsenetwork-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server