Skip to main content
Glama
Sign In
Cognitive Exoskeleton MCP Server

Cognitive Exoskeleton MCP Server

by hanjiang-215
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

detect_blindspots

Analyze a topic's coverage in your knowledge graph to identify blindspots, contradictions, and missing perspectives. Understand what you don't know.

Instructions

Analyze a topic's coverage in your knowledge graph and identify blindspots, contradictions, and missing perspectives. Helps you understand what you don't know about a subject.

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": {
      "topic": "<topic>"
    },
    "name": "detect_blindspots"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe topic to analyze for blindspots

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/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 implies a read-only analysis by using verbs like 'Analyze' and 'identify,' but it does not explicitly state that no data is modified, nor does it mention any prerequisites, permissions, or return format. This leaves some ambiguity about side effects.

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 sentences, front-loaded with the main action, and contains zero filler. Every clause adds meaningful information about the tool's purpose and benefit.

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 simple one-parameter tool with no output schema, the description conveys the core purpose and expected outcome. It could be more explicit about the form of the output (e.g., a report or list) and any limitations, but it is sufficient for an agent to understand when to invoke it.

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 parameter 'topic' described as 'The topic to analyze for blindspots.' The description merely reinforces this without adding new meaning or usage details. Baseline of 3 is appropriate because the schema already documents the parameter.

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 a specific action ('Analyze') on a specific resource ('coverage in your knowledge graph') and distinct outcomes ('blindspots, contradictions, and missing perspectives'). This differentiates it from sibling tools like query_mind or discover_connections, which focus on retrieval or connection-finding.

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

Usage Guidelines4/5

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

The phrase 'Helps you understand what you don't know about a subject' provides clear context for when to use this tool. However, it does not explicitly mention alternatives or conditions that would make another tool more appropriate, so it stops short of full when/when-not guidance.

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