Install
$ agentstack add skill-justnau1020-claude-os-new-mcp-tool ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →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.
- Author: justnau1020
- Source: justnau1020/claude-os
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.