Skip to main content
Glama
Sign In
Cognitive Exoskeleton MCP Server

Cognitive Exoskeleton MCP Server

by hanjiang-215
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

trace_concept_evolution

Trace how your understanding of a concept changes over time. Visualize belief shifts, key turning points, and the triggers that drive each change.

Instructions

Trace how your understanding of a concept has evolved over time. Shows a timeline of belief changes, key turning points, and what triggered each shift in understanding.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "concept": "<concept>"
    },
    "name": "trace_concept_evolution"
  }
}

Input Schema

NameRequiredDescriptionDefault
conceptYesThe concept name to trace evolution for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/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 and does disclose behavioral traits: it 'Shows a timeline of belief changes, key turning points, and what triggered each shift.' This goes beyond the name and gives useful expectations about the output. It does not mention underlying data sources or potential side effects, but the tool is clearly a read-only analysis operation.

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

Conciseness5/5

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

The description is two concise sentences, front-loaded with the main action and followed by concrete output details. Every phrase earns its place; no filler or redundancy.

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 low-complexity tool with one simple parameter and no output schema, the description is adequately complete. It states both the purpose and the nature of the returned information (timeline, turning points, triggers), so an agent has enough context to invoke it correctly.

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 coverage is 100% with the single parameter 'concept' described as 'The concept name to trace evolution for.' The description repeats this concept but adds no additional parameter semantics beyond what the schema already provides. Baseline 3 is appropriate.

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 uses a specific verb ('Trace') and resource ('concept evolution'), clearly distinguishing it from sibling tools like query_mind or discover_connections. It explicitly defines the tool's scope as temporal evolution of understanding.

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?

The description implies use when a user wants to see how their understanding of a concept has changed over time, but it does not explicitly contrast with siblings like query_mind or recall_context. No when-not-to-use guidance or alternative tool references are provided.

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