Skip to main content
Glama
dahshanlabs

klypix-mcp

by dahshanlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Brain lens — machine-readable views of a brain (freshness · provenance · activity · timeline · orrery · unresolved)

brain_lens

While the KLYPIX app (Windows) has the canvas open and lets AI tools use it, the freshness, provenance, activity, orrery and unresolved views come from KLYPIX itself — its own lens code over the cards this tool may see, the exact picture…

Instructions

While the KLYPIX app (Windows) has the canvas open and lets AI tools use it, the freshness, provenance, activity, orrery and unresolved views come from KLYPIX itself — its own lens code over the cards this tool may see, the exact picture the person sees (structured: true returns its full payload). Otherwise, the data twin of the desktop app's Brain Lenses: ONE structured payload any surface (agent, web viewer, iOS) can render. Views: freshness (age buckets + stale open ❓), provenance (who wrote the brain, by channel: you/claude/cursor/git/gardener/…), activity (last 7 days), timeline (birth-order events — the Replay spine; events included only for view:"timeline"), orrery (focus+context neighborhood of one card: 1/2/3-hop ring-capped nodes + typed edges — pass root as a card title prefix or id, defaults to the most-connected hub), unresolved (open-❓ triage, oldest first, with typed evidence). Read-only by construction — it never writes. Use it to answer "what's rotting / who wrote this / what happened this week / what's around X / what's undecided" with receipts, or to feed a UI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNoOrrery center: a card title prefix or id. Default: the most-connected hub card.
viewNoWhich lens to compute (default "all" — every section, timeline events omitted from structured output unless view is "timeline").
limitNoCap for recent-activity entries (default 30).
canvasNoCanvas filename/path. Defaults to the project brain ("brain").
staleDaysNoOpen questions older than this count as stale (default 21).
structuredNoAlso return the full machine-readable lens object (large — tens of KB). Default false: the markdown answers the question, and the object was previously attached to every call whether or not anything read it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses critical behaviors: read-only ('never writes'), that structured=true returns a large payload (tens of KB), and that the default markdown is lightweight. It also explains the conditional data source (KLYPIX vs data twin). Missing auth/rate limits, but for a read-only lens this is strong coverage.

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 one dense, run-on paragraph with nested clauses; the first sentence about KLYPIX conditions is not front-loaded and obscures the tool's main function. It lacks clear structure, making it harder to parse than necessary.

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

Completeness4/5

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

For a tool with six optional parameters and no output schema, the description covers the key facets: the available views, the structured flag's effect, and the default markdown output. It could go further in describing the exact markdown format or the structured object's shape, but it is largely complete for an agent to call it correctly.

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 adds value beyond the schema by explaining cross-parameter interactions: timeline events are only included for view:'timeline', and structured=true returns the full machine-readable object. It also describes root's role in orrery. This justifies a 4.

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 specifies the resource (brain) and enumerates the views (freshness, provenance, activity, timeline, orrery, unresolved), making it clear what the tool produces. However, it does not differentiate from sibling tools like brain_insights or brain_doctor, and the opening sentence about KLYPIX mixing sourcing conditions muddies the core purpose.

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?

It offers example questions ('what's rotting / who wrote this / what happened this week / what's around X / what's undecided') and mentions feeding a UI, which implies usage. But it provides no explicit when-not or alternative tool recommendations, leaving the agent to infer from siblings.

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

Deploy Server

Other Tools