Habitscore
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BASE_RPC_URL | No | Base RPC URL for balance reads and signing context. | https://mainnet.base.org |
| HABITSCORE_API_URL | No | API origin. | https://api.mydev-tools.tech |
| HABITSCORE_PRIVATE_KEY | No | Wallet private key for signing payments. Omit to start in quote-only mode. | |
| HABITSCORE_MAX_SPEND_USD | No | Hard cap per tool call in USD, enforced before signing. | 0.25 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_reliabilityA | Reliability analysis for up to 25 recurring tasks, jobs, pipelines or scheduled workflows in one call. Returns a reliability score and grade (healthy/degrading/unstable/failing) per task, lapse risk, streak recovery, latency-trend warnings, and remediation actions ranked by priority so the list is actionable top-down. Use for cron and pipeline monitoring, flaky-job triage, SLA and uptime adherence, agent task reliability, and deciding what to fix first. Deterministic threshold analysis over the figures you supply — no model, no log parsing, no root-cause inference. Costs $0.08 in USDC on Base. |
| analyze_behaviourA | Behavioural analysis over up to 25 habits or recurring activities in one call. Returns adherence and consistency scores, streak momentum, lapse-risk flags, highlights, watchouts and recommendations. Use for adherence monitoring, routine optimisation, engagement and churn-risk signals, and streak analysis. Costs $0.05 in USDC on Base. |
| recommend_next_actionsA | Ranked next-best action per habit, each with a rationale and a priority score. The cheapest endpoint, deterministic and CPU-only, so it is suitable for high-frequency loops. Costs $0.03 in USDC on Base. |
| extract_insightsA | Condensed behavioural highlights and watchouts — patterns, correlations and risk signals — without the full aggregate breakdown. Use when you want the narrative rather than the numbers. Costs $0.05 in USDC on Base. |
| build_habit_planB | Multi-week plan for ONE habit: weekly targets and dated milestones over a chosen horizon. The most compute-intensive endpoint. Costs $0.10 in USDC on Base. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
analyze_behaviour, extract_insights and recommend_next_actions all operate on the same habit data and return overlapping artefacts (highlights, watchouts, recommendations), so the boundary between 'full analysis', 'narrative only', and 'next actions only' requires reading descriptions carefully. analyze_reliability vs analyze_behaviour is clearer (tasks/jobs vs habits) but still conceptually adjacent.
All five names follow a strict verb_noun snake_case pattern (analyze_*, recommend_*, extract_*, build_*), so intent and grouping are immediately predictable. No mixed camelCase or vague single-word verbs.
Five tools is well within a healthy scope for an analysis-only service and each maps to a distinct output tier. Slight redundancy: extract_insights looks like a trimmed slice of analyze_behaviour rather than an independent capability.
Coverage is analysis-only: there is no way to record, update or query stored habit/task data, so every call must supply its own figures. Planning exists for a single habit but not for task/pipeline remediation or multi-habit plans, which leaves some obvious lifecycle gaps.