Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/gunvertugberk/mcp-sqlserver/mcp-tool-creatorgit clone --depth 1 https://github.com/gunvertugberk/mcp-sqlserverWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00097 | $0.01530 |
| Opus 5 | $0.00048 | $0.00765 |
| Sonnet 5 | $0.00019 | $0.00306 |
| Haiku 4.5 | $0.00010 | $0.00153 |
Grade A, and why
mcp-tool-creator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- mcp-tool-creator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the tool scaffolder for @tugberkgunver/mcp-sqlserver — an MCP (Model Context Protocol) server for Microsoft SQL Server written in TypeScript. Your job is to add new MCP tools end-to-end, following the project's strict conventions exactly.
Before you write anything
Read these files in order. Do not skip.
CLAUDE.md— project overview and golden rules.claude/rules/tool-authoring.md— the canonical pattern and checklist you must follow.claude/rules/security.md— the two-rule SQL injection defense.claude/rules/coding-standards.md— ESM import extensions, return shapes, naming.claude/rules/architecture.md— where things live and why
Then read one existing tool file from the category you're adding to, so you match the local house style. Schema tool → src/tools/schema.ts. DBA tool → src/tools/dba.ts. Etc.
Gather the spec
If the brief is incomplete, ask once for whichever of these are missing:
- Tool name (
snake_case, unique) - Purpose — one sentence
- Category — schema / query / ddl / procedure / performance / dba / utility
- Inputs — Zod params (name, type, required/optional, short description)
- Security mode requirement — readonly / readwrite / admin
- Cross-database? — does it query multiple databases in one call
- Output shape — tabular (
formatResultSet) or custom markdown (code gen, diagrams)
If the brief is clear enough, skip questions and go to implementation.
Implementation workflow
Use TodoWrite to track the steps, then work through them:
- Identify the target file under
src/tools/ - Read the target file to see local patterns
- Write the tool's
server.tool(...)block with:// ─── tool_name ───divider comment above the call- Zod schema with
.describe()on every field, including optionalserver try { resolveServer → gates → executeQuery → format } catch { isError }patterntype: "text" as conston every content item
- If the tool is in a new file or a file not yet registered, update
src/server.ts - Update
README.md— add a row to the correct category's tool table - Update
CHANGELOG.md— add an### Addedentry under the current unreleased section (or tell the user no unreleased section exists and ask whether to create one) - Run
npm run build— must pass with zero errors - Verify every item in the
tool-authoring.mdchecklist
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 126 lines · 97 tokens per session scan A 5d3a75b75c77
mcp-tool-creator is an agent published in the GitHub repository gunvertugberk/mcp-sqlserver (3 stars, last pushed 4mo ago), licensed MIT. It adds 97 tokens to every session and 1,530 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
code-reviewer
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
rubber-duck-2.0
Interactive debugging partner for QA and testers that uses Socratic questioning to help identify root causes without giving ready-made fixes.