Skip to main content
Glama

think

Structure complex problem-solving by organizing thoughts to analyze challenges and develop solutions within Claude Code MCP's software engineering environment.

Instructions

A tool for thinking through complex problems

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thoughtYesYour thoughts

Implementation Reference

  • The handler function for the "think" tool, which is a no-op that simply returns the provided thought as a response.
    async ({ thought }) => {
      return {
        content: [{ 
          type: "text", 
          text: `Thought process: ${thought}`
        }]
      };
    }
  • The input schema for the "think" tool, defining a single string parameter 'thought' using Zod.
    {
      thought: z.string().describe("Your thoughts")
    },
  • The registration of the "think" tool on the MCP server, including name, description, schema, and handler.
    server.tool(
      "think",
      "A tool for thinking through complex problems",
      {
        thought: z.string().describe("Your thoughts")
      },
      async ({ thought }) => {
        return {
          content: [{ 
            type: "text", 
            text: `Thought process: ${thought}`
          }]
        };
      }
    );
Behavior2/5

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

With no annotations, the description carries full burden but only states the tool is for 'thinking through complex problems,' without disclosing behavioral traits like whether it's read-only, has side effects, requires authentication, or produces output. This leaves significant gaps in understanding how the tool behaves.

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

Conciseness4/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized for a simple tool, though it could be more front-loaded with specific details to improve clarity.

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

Completeness2/5

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

Given the tool's conceptual nature, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'thinking through' results in, how the tool aids problem-solving, or what the agent should expect, leaving too much ambiguity for effective use.

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?

The schema description coverage is 100%, with the single parameter 'thought' described as 'Your thoughts.' The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema handles the parameter documentation adequately.

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

Purpose3/5

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

The description 'A tool for thinking through complex problems' states a general purpose but lacks specificity about what 'thinking through' entails or what resource it operates on. It distinguishes from siblings like 'bash' or 'readFile' by being about cognitive processing rather than file operations, but remains vague about the actual function.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for complex problems, but it doesn't specify contexts, prerequisites, or exclusions, leaving the agent to infer based on the tool name alone.

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/auchenberg/claude-code-mcp'

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