Skip to main content
Glama
Sign In
Think MCP

Think MCP

by GofMan5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Think Recall

think_recall
Read-only

Search active session or saved insights to recall prior reasoning, extensions, or alternatives, preventing redundant work and leveraging earlier conclusions.

Instructions

Read-only search of an active/explicit scope or saved insights.

Use before repeating work or relying on prior reasoning.

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": {
      "query": "<query>"
    },
    "name": "think_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
queryYesSearch query (fuzzy matching)
scopeNoWhere to searchsession
scopeIdNoExplicit scope id (session recall only)
searchInNoWhat to search (session only)all
thresholdNoMatch strictness (lower = stricter)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.6.0
    • addedInput schema / properties / scopeId
      Added value: +{
+  "description": "Explicit scope id (session recall only)",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

The description confirms the read-only nature ('Read-only search') as indicated by annotations (readOnlyHint=true) and adds context about scope types. No contradictions.

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?

Extremely concise with two sentences, front-loading the purpose. Every word adds value.

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?

Given the schema fully describes parameters, annotations present, and no output schema, the description adequately covers the tool's functionality for a read-only search.

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%, so baseline is 3. The description adds minimal parameter insight beyond 'saved insights' mapping to scope; no extra detail on limit, threshold, etc.

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 specifies a clear verb ('search') and resource ('active/explicit scope or saved insights'), distinguishing it from sibling tools like think and think_done.

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 description explicitly states when to use the tool: 'before repeating work or relying on prior reasoning.' It does not provide negative examples or alternatives, but the context is clear.

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