For example when using llm with ROOCODE don't known what is gogs, but the tools are loaded and ready to use.
Maybe enhance the tools description to the llm known that tool is belong to gogs
For example when using llm with ROOCODE don't known what is gogs, but the tools are loaded and ready to use.
Maybe enhance the tools description to the llm known that tool is belong to gogs
I'll enhance the tool descriptions to make it clear that all tools belong to the Gogs MCP server. This will help coding agents like ROOCODE understand the context better even if they're not familiar with Gogs.
My plan:
Review all tool descriptions in src/index.ts
Add "Gogs" prefix or context to tool names and descriptions where appropriate
Ensure descriptions clearly indicate these are Gogs API operations
Test the changes to ensure clarity
Starting work now...
@fszontagh I'm starting work on this issue now!
I'll enhance the tool descriptions to make it clear that all tools belong to the Gogs MCP server. This will help coding agents like ROOCODE understand the context better even if they're not familiar with Gogs.
My plan:
1. Review all tool descriptions in `src/index.ts`
2. Add "Gogs" prefix or context to tool names and descriptions where appropriate
3. Ensure descriptions clearly indicate these are Gogs API operations
4. Test the changes to ensure clarity
Starting work now...
I've successfully enhanced all tool descriptions to include "Gogs" context. This will help coding agents like ROOCODE understand what platform these tools interact with, even if they're not familiar with Gogs.
What Was Changed
Updated 83 tool descriptions in src/server.ts to explicitly mention "Gogs":
Examples:
❌ Before: "Get information about the authenticated user"
✅ After: "Get information about the authenticated user from Gogs"
❌ Before: "List issues in a repository"
✅ After: "List issues in a Gogs repository"
❌ Before: "Create a new organization"
✅ After: "Create a new Gogs organization"
Categories Updated
All tool categories now clearly indicate they work with Gogs:
✅ All 83 tool descriptions verified in compiled output
✅ Changes committed and pushed to repository
Commit
Commit fbe442d: feat: enhance tool descriptions with Gogs context #18
Now when LLMs see these tool names in their available tools list, they'll immediately understand these are Gogs API operations, making it easier for them to use the tools appropriately!
## ✅ Issue Resolved
I've successfully enhanced all tool descriptions to include "Gogs" context. This will help coding agents like ROOCODE understand what platform these tools interact with, even if they're not familiar with Gogs.
### What Was Changed
Updated **83 tool descriptions** in `src/server.ts` to explicitly mention "Gogs":
**Examples:**
- ❌ Before: `"Get information about the authenticated user"`
- ✅ After: `"Get information about the authenticated user from Gogs"`
- ❌ Before: `"List issues in a repository"`
- ✅ After: `"List issues in a Gogs repository"`
- ❌ Before: `"Create a new organization"`
- ✅ After: `"Create a new Gogs organization"`
### Categories Updated
All tool categories now clearly indicate they work with Gogs:
- 🔹 User Management → "Gogs user/users"
- 🔹 Repository Operations → "Gogs repository/repositories"
- 🔹 Issue Tracking → "Gogs issue/repository"
- 🔹 Labels & Milestones → "Gogs repository/issue"
- 🔹 Organizations & Teams → "Gogs organization/team"
- 🔹 Keys & Webhooks → "Gogs" context
- 🔹 Admin Operations → "Gogs user/organization/repository"
### Testing
- ✅ Build successful (no TypeScript errors)
- ✅ All 83 tool descriptions verified in compiled output
- ✅ Changes committed and pushed to repository
### Commit
Commit `fbe442d`: feat: enhance tool descriptions with Gogs context #18
Now when LLMs see these tool names in their available tools list, they'll immediately understand these are Gogs API operations, making it easier for them to use the tools appropriately!
Claude Coding Agent
For example when using llm with ROOCODE don't known what is gogs, but the tools are loaded and ready to use.
Maybe enhance the tools description to the llm known that tool is belong to gogs
@fszontagh I'm starting work on this issue now!
I'll enhance the tool descriptions to make it clear that all tools belong to the Gogs MCP server. This will help coding agents like ROOCODE understand the context better even if they're not familiar with Gogs.
My plan:
src/index.tsStarting work now...
✅ Issue Resolved
I've successfully enhanced all tool descriptions to include "Gogs" context. This will help coding agents like ROOCODE understand what platform these tools interact with, even if they're not familiar with Gogs.
What Was Changed
Updated 83 tool descriptions in
src/server.tsto explicitly mention "Gogs":Examples:
"Get information about the authenticated user"✅ After:
"Get information about the authenticated user from Gogs"❌ Before:
"List issues in a repository"✅ After:
"List issues in a Gogs repository"❌ Before:
"Create a new organization"✅ After:
"Create a new Gogs organization"Categories Updated
All tool categories now clearly indicate they work with Gogs:
Testing
Commit
Commit
fbe442d: feat: enhance tool descriptions with Gogs context #18Now when LLMs see these tool names in their available tools list, they'll immediately understand these are Gogs API operations, making it easier for them to use the tools appropriately!