agent-reasoning-mcp
Related Servers
Alternatives to agent-reasoning-mcp
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceGoal-oriented narrative state machine for AI agents, exposing live world/scene context as MCP tools and resources.-
- AlicenseNot gradedqualityDmaintenanceObjective-driven cognitive architecture engine that builds single experts, councils, or full autonomous organizations from user goals, generating deployment-ready superprompts and configurations.8 npmMIT
- AlicenseAqualityAmaintenanceHigh-frequency (~60Hz) in-browser behavior tree execution engine for autonomous AI agents. Reactive priority interrupts, safety guardrails & deterministic action replay over MCP.109,149 npm23MIT
- FlicenseAqualityCmaintenanceEnables AI agents to hand high-level objectives to a decision-making core that autonomously reasons, plans, enforces deterministic policy, executes capabilities, evaluates outcomes, and persists semantic memory over stdio or Streamable HTTP.6-
- AlicenseAqualityCmaintenanceCampaign orchestration MCP server for AI agents — dependency DAGs, parallel fan-out, failure policies, and embedded notes.21GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to decompose high-level goals into structured task plan DAGs with dependencies, acceptance criteria, and quality gates, and to validate or export those plans in multiple formats.MIT
TDQS
Scored across 15 tools
Most tools target distinct concepts, and the descriptions actively disambiguate with explicit 'use X instead of Y' guidance (e.g. assess_risk vs evaluate_situation, set_goal vs manage_intentions). However there is a dense cluster of risk/utility evaluation tools (assess_risk, evaluate_situation, ask_score, gate_intention) that an agent could still misselect among.
The set consistently uses snake_case verb_noun patterns (manage_beliefs, query_knowledge, get_decision_trace, set_utility_weights), with coherent families like ask_* and manage_*. Minor deviations are bare verbs (replan, classify) and an unusual token (ask_noul), but overall the convention is predictable.
15 tools sit at the upper edge of the comfortable 3-15 range but are justified by a genuinely broad cognitive-architecture domain (risk, beliefs, goals, intentions, knowledge, DB ops). It is slightly heavy but each tool maps to a real capability rather than being filler.
Coverage is strong: beliefs (update/query/expire/reconcile), goals (create/update/decompose/get/list/abandon), intentions (create/dispatch/get/list/cancel/resolve) and traces/knowledge all form coherent lifecycles. Gaps are minor—no obvious delete or bulk-export for some resources—but core reasoning workflows are well covered.