AgentStack
SKILL verified Apache-2.0 Self-run

New Mcp Tool

skill-justnau1020-claude-os-new-mcp-tool · by justnau1020

Add a new MCP tool to a FastMCP server. Use when adding a new tool for LLM agents or extending the MCP interface with new functionality.

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-justnau1020-claude-os-new-mcp-tool

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of New Mcp Tool? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Add a New MCP Tool

Add a tool to the project's FastMCP server.

Arguments

  • $ARGUMENTS -- Tool name in snake_case (e.g., get_user_profile)

Steps

1. Read the existing MCP server

Read the MCP server file to understand current tool patterns and the FastMCP setup.

2. Add the tool

@mcp.tool()
async def $ARGUMENTS(
    param1: str,
    param2: int = 10,
) -> str:
    """Clear description of what this tool does and when an LLM should use it.

    Include example parameter values to help LLMs understand expected input.
    Example: param1="example_value", param2=30
    """
    ...

3. Tool description conventions

The tool description is critical -- it's how LLMs decide when to call it:

  • First sentence: what the tool does
  • Second sentence: when to use it
  • Include parameter examples inline
  • Mention any constraints (rate limits, data availability)

4. Implementation conventions

  • Async only: All tool functions must be async def
  • Return strings: MCP tools return string responses for LLM consumption
  • Actionable errors: If something fails, return a helpful error string, not a generic one
  • Respect data boundaries: All data queries should respect the project's access control and data validation rules

5. Write tests

Add tests for the new tool's logic. Test:

  • Happy path with valid parameters
  • Error handling with invalid parameters
  • Data validation on returned data

6. Verify

pytest tests/ -v -k "mcp"

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.