Skip to main content
Glama
enesjakozh
auchenberg

Claude Code MCP

by auchenberg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

クロード・コード MCP

Claude Code MCPは、 Claude Codeをモデルコンテキストプロトコル（MCP）サーバーとして実装したものです。このプロジェクトでは、標準化されたMCPインターフェースを通じて、Claude Codeの強力なソフトウェアエンジニアリング機能を利用できます。

⚠️免責事項⚠️

Claude Code MCP は、Claude Code のコードベースを分析し、MCP サーバーを生成するように促された DevinAI によって自動生成されたプロジェクトです。

これは概念実証であり、誰にも使用を勧めません。

クロード・コードとは何ですか?

Claude Codeは、ClaudeをベースにしたAnthropicのソフトウェアエンジニアリングタスク向けCLIツールです。開発者を支援するツールと機能のセットを提供します。

  • コード生成と編集

  • コードレビューと分析

  • デバッグとトラブルシューティング

  • ファイルシステム操作

  • シェルコマンドの実行

  • プロジェクトの探索と理解

元の実装は、Claude の API と対話するためのプロンプトとツールを定義する JavaScript モジュールとして利用できます。

Related MCP server: MCP Tool

MCPとは何ですか?

モデルコンテキストプロトコル（MCP）は、AIモデル用の標準化されたインターフェースであり、異なるモデルやプロバイダー間で一貫したインタラクションパターンを実現します。MCPは次のものを定義します。

  • ツール: モデルがアクションを実行するために呼び出すことができる関数

  • リソース: モデルがアクセスできる外部データ

  • プロンプト: 事前定義された会話テンプレート

Claude Code を MCP サーバーとして実装することにより、その機能を MCP 互換のあらゆるクライアントで利用できるようになり、相互運用性と柔軟性が向上します。

特徴

  • Claude Code 機能を MCP サーバーとして完全に実装

  • ファイル操作、シェルコマンド、コード分析のためのツールを提供します

  • ファイルシステムと環境情報にアクセスするためのリソースを公開します

  • 一般的な CLI 操作とコードレビューのためのプロンプトが含まれています

  • あらゆるMCPクライアントと互換性あり

  • 完全な型安全性を備えたTypeScript実装

インストール

# Clone the repository
git clone https://github.com/auchenberg/claude-code-mcp.git
cd claude-code-mcp

# Install dependencies
npm install

# Build the project
npm run build

使用法

スタンドアロンサーバーとして実行

# Start the server
npm start

MCPクライアントでの使用

Claude Code MCPは、どのMCPクライアントでも使用できます。MCP TypeScript SDKを使用して接続する方法の例を以下に示します。

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";

const transport = new StdioClientTransport({
  command: "node",
  args: ["dist/index.js"]
});

const client = new Client(
  {
    name: "example-client",
    version: "1.0.0"
  },
  {
    capabilities: {
      prompts: {},
      resources: {},
      tools: {}
    }
  }
);

await client.connect(transport);

// Use Claude Code through MCP
const result = await client.callTool({
  name: "bash",
  arguments: {
    command: "ls -la"
  }
});

console.log(result);

利用可能なツール

Claude Code MCP は次のツールを提供します。

  • bash : セキュリティ制限とタイムアウトオプション付きでシェルコマンドを実行する

  • readFile : 行オフセットと制限のオプションを使用してファイルシステムからファイルを読み取ります

  • listFiles : 詳細なメタデータを含むファイルとディレクトリを一覧表示する

  • searchGlob : globパターンに一致するファイルを検索する

  • grep : 正規表現パターンをサポートしたファイル内のテキストを検索する

  • think : 複雑な問題を考えるためのノーオペレーションツール

  • codeReview : バグ、セキュリティ問題、ベストプラクティスについてコードを分析およびレビューします

  • editFile : 指定された内容のファイルを作成または編集する

ツールの詳細

バッシュ

{
  command: string;  // The shell command to execute
  timeout?: number; // Optional timeout in milliseconds (max 600000)
}

bash ツールには、 curl 、 wgetなどの潜在的に危険なコマンドの実行を防ぐセキュリティ制限が含まれています。

ファイル読み取り

{
  file_path: string; // The absolute path to the file to read
  offset?: number;   // The line number to start reading from
  limit?: number;    // The number of lines to read
}

サーチグロブ

{
  pattern: string;  // The glob pattern to match files against
  path?: string;    // The directory to search in (defaults to current working directory)
}

グレップ

{
  pattern: string;   // The regular expression pattern to search for
  path?: string;     // The directory to search in (defaults to current working directory)
  include?: string;  // File pattern to include in the search (e.g. "*.js", "*.{ts,tsx}")
}

利用可能なリソース

  • file : ファイルの内容にアクセスする ( file://{path} )

    • 適切なエラー処理によりファイルの内容に直接アクセス可能

    • 指定されたファイルの全テキストコンテンツを返します

  • ディレクトリ: ディレクトリの内容を一覧表示します ( dir://{path} )

    • ファイル情報オブジェクトのJSON配列を返します

    • 各オブジェクトには、名前、パス、isDirectory、サイズ、変更日が含まれます。

  • environment : システム環境情報を取得する ( env://info )

    • システム環境に関する情報を返します

    • Node.js バージョン、npm バージョン、OS 情報、環境変数が含まれます

利用可能なプロンプト

  • generalCLI : Claude Code の一般的な CLI プロンプト

    • Claude が CLI ツールとして機能するための包括的なシステム プロンプトを提供します。

    • 口調、スタイル、積極性、慣習の遵守に関するガイドラインが含まれています

    • 環境の詳細を自動的に含めます

  • codeReview : コードのレビューを促す

    • コードレビュータスクに特化したプロンプト

    • バグ、セキュリティの脆弱性、パフォーマンスの問題、ベストプラクティスについてコードを分析します

  • prReview : プルリクエストのレビューを促す

    • PRレビュータスクに特化したプロンプト

    • PRの変更を分析し、包括的なフィードバックを提供します

  • initCodebase : コードベースのドキュメントを含む新しいCLAUDE.mdファイルを初期化します。

    • ビルド/lint/テストコマンドとコードスタイルガイドラインのドキュメントを作成します

    • Claude Codeで新しいプロジェクトを立ち上げる際に便利です

発達

# Run in development mode with auto-reload
npm run dev

建築

Claude Code MCP はモジュラー アーキテクチャで構築されています。

claude-code-mcp/
├── src/
│   ├── server/
│   │   ├── claude-code-server.ts  # Main server setup
│   │   ├── tools.ts               # Tool implementations
│   │   ├── prompts.ts             # Prompt definitions
│   │   └── resources.ts           # Resource implementations
│   ├── utils/
│   │   ├── bash.ts                # Shell command utilities
│   │   └── file.ts                # File system utilities
│   └── index.ts                   # Entry point
├── package.json
├── tsconfig.json
└── README.md

実装は、次の主要な原則に従います。

  1. モジュール性: 各コンポーネント（ツール、プロンプト、リソース）は個別のモジュールに実装されます。

  2. 型安全性: すべてのコンポーネントの完全なTypeScript型定義

  3. エラー処理: すべての操作に対する包括的なエラー処理

  4. セキュリティ: 潜在的に危険な操作に対するセキュリティ制限

実装の詳細

MCPサーバーのセットアップ

メインサーバーはclaude-code-server.tsでセットアップされます。

export async function setupClaudeCodeServer(server: McpServer): Promise<void> {
  // Set up Claude Code tools
  setupTools(server);
  
  // Set up Claude Code prompts
  setupPrompts(server);
  
  // Set up Claude Code resources
  setupResources(server);
}

ツールの実装

ツールは、MCP SDK のツール登録方法を使用して実装されます。

server.tool(
  "toolName",
  "Tool description",
  {
    // Zod schema for tool arguments
    param1: z.string().describe("Parameter description"),
    param2: z.number().optional().describe("Optional parameter description")
  },
  async ({ param1, param2 }) => {
    // Tool implementation
    return {
      content: [{ type: "text", text: "Result" }]
    };
  }
);

リソース実装

リソースは、MCP SDK のリソース登録メソッドを使用して実装されます。

server.resource(
  "resourceName",
  new ResourceTemplate("resource://{variable}", { list: undefined }),
  async (uri, variables) => {
    // Resource implementation
    return {
      contents: [{
        uri: uri.href,
        text: "Resource content"
      }]
    };
  }
);

ライセンス

マサチューセッツ工科大学

謝辞

貢献

貢献を歓迎します！お気軽にプルリクエストを送信してください。

免責事項

このプロジェクトはAnthropicと公式に提携していません。Claude CodeはAnthropicの製品であり、このプロジェクトはClaude CodeをMCPサーバーとして独立して実装したものです。

Available Tools

8 tools
bashC

Execute a shell command

ParametersJSON Schema
NameRequiredDescriptionDefault
commandYesThe shell command to execute
timeoutNoOptional timeout in milliseconds (max 600000)

TDQS

C2.9/5.0
Behavior2/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. 'Execute a shell command' implies a potentially powerful and risky operation, but the description doesn't mention security implications, permission requirements, side effects, or what happens on timeout. This is a significant gap for a tool that can perform arbitrary system operations.

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 extremely concise at just three words, with zero wasted language. It's front-loaded with the essential purpose and doesn't include any unnecessary elaboration, making it efficient for quick understanding.

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?

For a tool that executes arbitrary shell commands with no annotations and no output schema, the description is inadequate. It doesn't address the significant behavioral complexity, security implications, or what the tool returns. Given the power and risk of this operation, more context is needed for safe and 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%, so the schema already documents both parameters thoroughly. The description doesn't add any additional meaning beyond what's in the schema - it doesn't explain command syntax, shell environment, or timeout behavior. This meets the baseline for high schema coverage.

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 'Execute a shell command' clearly states the verb ('execute') and resource ('shell command'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling tools that might also execute commands or interact with the shell environment, keeping it from a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'editFile' or 'listFiles'. There's no mention of prerequisites, safety considerations, or typical use cases, leaving the agent with minimal context for appropriate tool selection.

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

codeReviewC

Review code for bugs, security issues, and best practices

ParametersJSON Schema
NameRequiredDescriptionDefault
codeYesThe code to review

TDQS

C2.9/5.0
Behavior2/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 states the tool reviews code but doesn't describe how it operates (e.g., static analysis, AI-based review), what permissions or resources it requires, or the format of results. This leaves significant gaps in understanding the tool's behavior.

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 waste. It's appropriately sized for a simple tool, though it could be slightly more structured (e.g., by listing review aspects in bullet points) for better 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 complexity (code review can involve nuanced analysis), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the review outputs (e.g., a list of issues, a summary), how comprehensive it is, or any limitations, making it inadequate for full contextual understanding.

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 input schema has 100% description coverage, with the 'code' parameter fully documented in the schema. The description adds no additional meaning beyond the schema, such as code language support or review depth, so it meets the baseline score of 3 for high schema coverage.

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 clearly states the tool's purpose with specific verbs ('review code') and resources ('bugs, security issues, and best practices'), making it easy to understand what the tool does. However, it doesn't differentiate from potential sibling tools like 'think' or 'bash' that might also analyze code, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for code review, or compare it to sibling tools like 'think' for analysis or 'bash' for execution, leaving the agent with minimal usage direction.

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

editFileC

Create or edit a file

ParametersJSON Schema
NameRequiredDescriptionDefault
file_pathYesThe absolute path to the file to edit
contentYesThe new content for the file

TDQS

C2.9/5.0
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 operation without behavioral details. It doesn't disclose whether this overwrites existing files, requires specific permissions, handles errors, or has side effects like creating directories. The vague 'create or edit' leaves critical behavior ambiguous.

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 extremely concise with just three words, front-loaded and zero waste. Every word earns its place by conveying the core action and resource efficiently.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavior, error handling, or output format, leaving significant gaps for an agent to use it correctly in context with siblings.

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 description coverage is 100%, so the schema fully documents both parameters ('file_path' and 'content'). The description adds no additional meaning beyond implying these parameters are used for the operation, meeting the baseline for high schema coverage.

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 clearly states the tool's purpose with specific verbs ('create or edit') and resource ('a file'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'readFile' or 'listFiles' beyond the basic operation type.

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 guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., file permissions), when editing is preferred over creating, or how it relates to siblings like 'readFile' for viewing or 'bash' for file operations.

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

grepC

Search for text in files

ParametersJSON Schema
NameRequiredDescriptionDefault
patternYesThe regular expression pattern to search for in file contents
pathNoThe directory to search in. Defaults to the current working directory.
includeNoFile pattern to include in the search (e.g. "*.js", "*.{ts,tsx}")

TDQS

C2.9/5.0
Behavior2/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. 'Search for text in files' implies a read-only operation, but it doesn't specify whether this is safe, if it requires permissions, how it handles errors, or what the output format looks like. For a tool with three parameters and no annotations, this is a significant gap in behavioral context.

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 a single, efficient sentence with zero waste—'Search for text in files' is front-loaded and perfectly concise. Every word earns its place by directly conveying the core functionality without unnecessary elaboration.

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 complexity (3 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what the tool returns (e.g., matches, line numbers, file names), how results are formatted, or any behavioral nuances like case sensitivity or recursion. For a search tool, this leaves critical gaps for an AI agent to use it effectively.

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 description adds no parameter-specific information beyond what's already in the schema, which has 100% coverage with clear descriptions for 'pattern', 'path', and 'include'. According to the rules, when schema description coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 'Search for text in files' clearly states the verb (search) and resource (text in files), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'searchGlob' or 'listFiles' that might also involve searching or file operations, so it doesn't reach the highest level of sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like 'searchGlob' or 'listFiles'. There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage based solely on the tool name and basic purpose.

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

listFilesC

Lists files and directories in a given path

ParametersJSON Schema
NameRequiredDescriptionDefault
pathYesThe absolute path to the directory to list

TDQS

C2.9/5.0
Behavior2/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 states the basic action but doesn't describe key behaviors like whether it returns recursive listings, handles symbolic links, includes hidden files, or what happens if the path is invalid. This leaves significant gaps for an agent to understand how the tool behaves beyond the simple listing.

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 a single, clear sentence that directly states the tool's function without any unnecessary words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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 lack of annotations and output schema, the description is incomplete for a tool that performs file system operations. It doesn't address important contextual aspects like error handling, output format, or behavioral details (e.g., recursion, hidden files), which are crucial for an agent to use this tool effectively in real scenarios.

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 input schema has 100% description coverage, with the 'path' parameter clearly documented as 'The absolute path to the directory to list'. The description adds no additional semantic information beyond what the schema provides, so it meets the baseline for adequate but unenhanced parameter documentation.

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 clearly states the action ('Lists') and the target ('files and directories in a given path'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential siblings like 'searchGlob' or 'grep' that might also involve file operations, so it doesn't achieve full differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like 'searchGlob' or 'grep'. It lacks any context about prerequisites, such as whether the path must exist or be accessible, or when other tools might be more appropriate for similar tasks.

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

readFileC

Read a file from the local filesystem

ParametersJSON Schema
NameRequiredDescriptionDefault
file_pathYesThe absolute path to the file to read
offsetNoThe line number to start reading from
limitNoThe number of lines to read

TDQS

C2.9/5.0
Behavior2/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 states the basic action but lacks details on error handling (e.g., for missing files), performance considerations, or output format (e.g., text vs. binary). This leaves significant gaps in understanding how the tool behaves in practice.

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 a single, direct sentence with no wasted words, making it highly efficient and easy to parse. It front-loads the core purpose without unnecessary elaboration, which is ideal for quick understanding.

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 complexity (file I/O with parameters) and lack of annotations and output schema, the description is insufficient. It doesn't cover critical aspects like return values, error cases, or security implications, leaving the agent poorly equipped to use the tool effectively in real scenarios.

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 clear descriptions for all parameters (file_path, offset, limit). The description doesn't add any semantic details beyond what the schema provides, such as explaining how offset and limit interact or file encoding issues. This meets the baseline for high schema coverage.

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 clearly states the action ('Read') and resource ('a file from the local filesystem'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'grep' or 'searchGlob' that also involve file reading operations, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'grep' for searching or 'listFiles' for directory contents. There's no mention of prerequisites, such as file existence or permissions, which leaves the agent without context for appropriate tool selection.

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

searchGlobC

Search for files matching a pattern

ParametersJSON Schema
NameRequiredDescriptionDefault
patternYesThe glob pattern to match files against
pathNoThe directory to search in. Defaults to the current working directory.

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool searches for files but doesn't describe how it behaves—e.g., whether it returns full paths, file contents, or metadata; if it's recursive or case-sensitive; or any performance or permission considerations. This leaves significant gaps for an agent to understand the tool's behavior.

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 a single, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It is appropriately sized and front-loaded, making it easy for an agent to quickly grasp the core functionality.

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 complexity of a file search tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a list of file paths or details), how errors are handled, or any behavioral nuances. This makes it inadequate for an agent to fully understand the tool's context and usage.

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 input schema has 100% description coverage, with clear documentation for both parameters ('pattern' and 'path'). The description adds no additional meaning beyond the schema, such as examples of glob patterns or path constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 'Search for files matching a pattern' clearly states the verb ('search') and resource ('files'), specifying the action and target. However, it doesn't distinguish this tool from sibling tools like 'grep' or 'listFiles', which might offer similar file-searching capabilities, so it lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to prefer 'searchGlob' over 'grep' for pattern matching or 'listFiles' for file listing, nor does it specify any prerequisites or exclusions for usage.

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

thinkC

A tool for thinking through complex problems

ParametersJSON Schema
NameRequiredDescriptionDefault
thoughtYesYour thoughts

TDQS

C2.6/5.0
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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 8 tool updates
    • First observedbash
    • First observedcodeReview
    • First observededitFile
    • First observedgrep
    • First observedlistFiles
    • First observedreadFile
    • First observedsearchGlob
    • First observedthink
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 8 tools

Disambiguation4/5

Most tools have distinct purposes, such as bash for shell execution, codeReview for analysis, and file operations like editFile, readFile, and listFiles. However, grep and searchGlob could be slightly confusing as both involve searching, though grep targets text content while searchGlob focuses on file patterns, which is clarified in descriptions.

Naming Consistency3/5

The naming is mixed with camelCase (codeReview, editFile, readFile, listFiles, searchGlob) and lowercase (bash, grep, think), lacking a uniform pattern. While the camelCase tools follow a verbNoun style, the inconsistency in case usage reduces predictability across the set.

Tool Count5/5

With 8 tools, the count is well-scoped for a code and file management server, covering essential operations like execution, review, file handling, and search. Each tool serves a clear purpose without feeling excessive or insufficient for the domain.

Completeness4/5

The toolset provides strong coverage for code and file workflows, including creation, reading, editing, listing, searching, and review. A minor gap is the lack of a deleteFile tool, which agents might need to work around, but core operations are well-represented.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches