Skip to main content
Glama
Andreymi

tractatus_thinking

by Andreymi

tractatus_thinking

Decompose complex concepts into atomic propositions to reveal logical structure, expose hidden dependencies, and eliminate fuzzy definitions.

Instructions

A powerful tool for logical concept analysis and structured thinking.

This tool helps you break down complex ideas into their fundamental components, revealing the logical structure beneath. Each component can be analyzed, refined, and reorganized as your understanding deepens.

When to use this tool:

  • Breaking down complex concepts into atomic truths

  • Understanding with room for restructuring

  • Analysis where bundled ideas hide the real problem

  • Concepts where the logical structure isn't clear initially

  • Problems that require multiplicative understanding

  • Tasks that need to separate essential from accidental

  • Situations where fuzzy definitions cause confusion

Key features:

  • You can restructure propositions as understanding evolves

  • You can separate bundled concepts at any level

  • You can reveal dependencies between propositions

  • You can express logical relationships precisely

  • Not every proposition needs to decompose further - some are atomic

  • Discovers multiplicative relationships (A × B × C)

  • Reveals what must ALL be true simultaneously

  • Shows the logical architecture beneath surface complexity

  • Provides structural clarity

Benchmark insights - This tool excels at:

  • Revealing multiplicative failures (why ALL factors must align for success)

  • Creating precise definitions that eliminate team confusion

  • Finding the ONE missing element preventing success

  • Understanding logical necessity vs mere correlation

  • Decomposing fuzzy concepts into measurable components

  • Showing WHY things work, not just HOW they work

Strategic sequencing (proven in benchmarks):

  • Use THIS FIRST to understand WHAT you're dealing with

  • Then apply process thinking for HOW to proceed

  • Return here to formalize and verify your solution structure

Complementary to sequential thinking:

  • This tool analyzes WHAT (structure/logic) while sequential thinking handles HOW (process/steps)

  • Start here for conceptual clarity, switch to sequential for implementation planning

  • Together they form a complete thinking system: structure → process → verification

You should:

  1. Start here when concepts feel fuzzy or bundled - structure guides process

  2. Use this BEFORE planning implementation - understanding WHAT enables HOW

  3. Look for multiplicative relationships (A × B × C) that explain persistent failures

  4. Separate what MUST be true from what HAPPENS to be true

  5. Mark propositions that are truly atomic and cannot decompose further

  6. Identify which factors must ALL be present vs which are additive

  7. Generate the logical structure progressively as patterns emerge

  8. Verify you've found the real dependencies, not just correlations

  9. Refine the hierarchy when you discover hidden relationships

  10. Provide structural insight that explains WHY, not just WHAT

  11. Switch to process thinking once structure is clear, return here to verify

Operations: start (reveal structure), add (build understanding), analyze (check completeness), export (capture insights), navigate (explore relationships), revise (refine), undo (reconsider), move (restructure).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoOptional: Analysis style (default: analytical)analytical
formatNoExport formatmarkdown
targetNoNavigation target: proposition number, "parent", "child", "sibling", or "root" (required for "navigate")
conceptNoThe concept or question to analyze - just pass any "What is X?" question
contentNoThe proposition content (required for "add" operation)
thoughtsNoOptional: Your raw thoughts for instant analysis (quick mode)
is_atomicNoWhether proposition cannot be decomposed further
operationYesOperation to perform
confidenceNoConfidence level
session_idNoThe session ID (required for add, navigate, export, analyze operations)
child_indexNoIndex of child to navigate to (when target is "child")
depth_limitNoOptional: Maximum depth (default: 5)
new_contentNoNew content for the proposition (required for revise operation)
new_positionNoPosition among siblings at new location (optional)
parent_numberNoParent proposition number (optional for "add" operation)
include_metadataNoInclude analysis metadata in export
confirm_orphaningNoConfirm that orphaning propositions is acceptable (optional)
new_parent_numberNoNew parent proposition number, or null for root level (optional for move operation)
preserve_childrenNoWhether to preserve child propositions during revision (optional, default true)
decomposition_typeNoType of logical decomposition
proposition_numberNoThe proposition number to revise (required for revise operation)
validate_coherenceNoWhether to validate coherence with children (optional, default true)
confidence_thresholdNoOptional: Minimum confidence (default: 0.3)
Behavior4/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 goes beyond the schema by explaining capabilities (restructure, separate bundled concepts, reveal dependencies), limitations (some propositions are atomic), and operational nuances (multiplicative relationships, progressive structure generation). However, it does not disclose return formats, session management details, or error behaviors, which would be needed 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.

Conciseness2/5

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

The description is excessively verbose and repetitive. Phrases like 'structural clarity', 'logical architecture', and 'multiplicative relationships' are repeated across multiple bullet lists. While it is well-structured with headers and bullets, many sentences do not earn their place, making it longer than necessary.

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?

The tool is complex (23 parameters, no output schema, no annotations), and the description provides substantial strategic context for when and why to use it. However, it lacks operational specificity: it does not explain what each operation returns, how sessions are managed, or how to chain operations in practice. This leaves notable gaps in the full usage picture.

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%, so the baseline is 3. The description adds high-level operational context (lists operations like start, add, export) but does not provide parameter-specific meaning beyond what the schema already contains. It neither detracts nor significantly enhances parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'logical concept analysis and structured thinking' and 'break down complex ideas into their fundamental components'. It uses specific verbs like analyze and decompose, and identifies the resource as logical concepts. Although there are no siblings, it sufficiently distinguishes itself from generic thinking tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance, including a dedicated 'When to use this tool' section and a 'Strategic sequencing' section that explains when to use this tool versus sequential thinking. It even names the alternative ('sequential thinking') and describes the complementary relationship, making usage boundaries clear.

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/Andreymi/tractatus-thinking'

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