Skip to main content
Glama
Ijongwon

MCP Practice

by Ijongwon
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

mcp-practice

A Model Context Protocol (MCP) server built with mcp-framework.

Quick Start

# Install dependencies
npm install

# Build the project
npm run build

Related MCP server: Scenario Word

Project Structure

mcp-practice/
├── src/
│   ├── tools/        # MCP Tools
│   │   └── ExampleTool.ts
│   └── index.ts      # Server entry point
├── package.json
└── tsconfig.json

Adding Components

The project comes with an example tool in src/tools/ExampleTool.ts. You can add more tools using the CLI:

# Add a new tool
mcp add tool my-tool

# Example tools you might create:
mcp add tool data-processor
mcp add tool api-client
mcp add tool file-handler

Tool Development

Example tool structure:

import { MCPTool } from "mcp-framework";
import { z } from "zod";

interface MyToolInput {
  message: string;
}

class MyTool extends MCPTool<MyToolInput> {
  name = "my_tool";
  description = "Describes what your tool does";

  schema = {
    message: {
      type: z.string(),
      description: "Description of this input parameter",
    },
  };

  async execute(input: MyToolInput) {
    // Your tool logic here
    return `Processed: ${input.message}`;
  }
}

export default MyTool;

Publishing to npm

  1. Update your package.json:

    • Ensure name is unique and follows npm naming conventions

    • Set appropriate version

    • Add description, author, license, etc.

    • Check bin points to the correct entry file

  2. Build and test locally:

    npm run build
npm link
mcp-practice  # Test your CLI locally

  3. Login to npm (create account if necessary):

    npm login

  4. Publish your package:

    npm publish

After publishing, users can add it to their claude desktop client (read below) or run it with npx


## Using with Claude Desktop

### Local Development

Add this configuration to your Claude Desktop config file:

**MacOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
**Windows**: `%APPDATA%/Claude/claude_desktop_config.json`

```json
{
  "mcpServers": {
    "mcp-practice": {
      "command": "node",
      "args":["/absolute/path/to/mcp-practice/dist/index.js"]
    }
  }
}

After Publishing

Add this configuration to your Claude Desktop config file:

MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-practice": {
      "command": "npx",
      "args": ["mcp-practice"]
    }
  }
}

Building and Testing

  1. Make changes to your tools

  2. Run npm run build to compile

  3. The server will automatically load your tools on startup

Learn More

Available Tools

1 tool
generate_commit_messageC

Generate standardized commit message

ParametersJSON Schema
NameRequiredDescriptionDefault
workingDirectoryYesThe absolute path of the project root directory, for example: /Users/yourname/projects/yourproject

TDQS

C2.6/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 'Generate' but doesn't clarify if this is a read-only operation (e.g., analyzing Git history) or a write operation (e.g., creating a commit file). It also omits details like whether it requires Git to be initialized, handles errors, or has side effects, which are critical for a tool with no annotation coverage.

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 with no wasted words, making it appropriately concise. However, it could be more front-loaded with critical details (e.g., behavioral traits) given the lack of annotations, but as-is, it's structurally sound.

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 generating commit messages (which may involve Git operations, formatting rules, or user input), the description is incomplete. With no annotations, no output schema, and minimal behavioral context, it fails to provide enough information for an agent to use the tool confidently, especially for a task that could have varied implementations.

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 parameter 'workingDirectory' clearly documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., it doesn't explain why this path is needed or how it influences the generation). With high schema coverage, 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.

Purpose3/5

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

The description 'Generate standardized commit message' states a clear verb ('Generate') and resource ('standardized commit message'), providing a basic understanding of the tool's function. However, it lacks specificity about what 'standardized' means (e.g., conventional commits, specific formatting rules) and doesn't distinguish from any siblings (though none exist), making it somewhat vague.

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 or any context for its application. It doesn't mention prerequisites (e.g., Git repository status), exclusions, or typical scenarios, leaving the agent with no usage direction beyond the basic purpose.

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. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedgenerate_commit_message
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly distinct by default.

Naming Consistency5/5

A single tool inherently has consistent naming, as there are no other tools to compare it against. The name follows a clear verb_noun pattern.

Tool Count2/5

One tool is too few for a server named 'MCP Practice', which suggests a broader scope or practice set. A single tool feels thin and inadequate for meaningful practice or functionality.

Completeness2/5

The tool surface is severely incomplete; a single commit message generator does not cover any meaningful domain or workflow. There are significant gaps, making it impractical for most agent tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Calculator MCP Server

    QuantGeekDev
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server built with mcp-framework that allows users to create and manage custom tools for processing data, integrating with the Claude Desktop via CLI.
    23
    5
    MIT

  • my-mcp-server

    15972289829
    F
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.
    88
    -

  • My MCP Server

    goodafternoonoo
    F
    license
    Not graded
    quality
    D
    maintenance
    A customizable Model Context Protocol server built with mcp-framework that enables Claude to access external tools and capabilities through a standardized interface.
    88
    -

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/Ijongwon/mcp-practice'

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