K4G Application Triage MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| k4g_search_applicationsA | Search the incubator application pipeline by text, sector, stage, or score. This tool searches across all applications in the current cycle. It does NOT modify any data - use k4g_flag_for_review for that. Args:
Returns JSON with: { total, count, applications: [ { id, org_name, founder_name, country, food_sector, one_liner, stage, review_status, assigned_reviewer, impact_score, feasibility_score, team_score } ] } Examples:
|
| k4g_get_applicationA | Fetch full detail for a single application by ID, including all reviewer notes. Args:
Returns the full application record as JSON, including the notes array. Error Handling:
|
| k4g_list_pending_reviewA | List applications that still need a decision: review_status is 'pending_review' or 'flagged_for_discussion'. This is the tool to answer "what's stuck in the queue" - it does not include applications already marked 'reviewed'. Args:
Returns JSON with: { count, applications: [ ...summaries, sorted oldest submitted_date first ] } Examples:
|
| k4g_flag_for_reviewA | Mark an application as 'flagged_for_discussion' and attach a reviewer note explaining why. This changes the application's review_status - it is not read-only. Use it when an application needs a second opinion or a full-panel discussion rather than a solo decision. Args:
Returns the updated application record as JSON. Error Handling:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: search finds applications by criteria, get fetches full details by ID, list surfaces pending decision items, and flag modifies review status. There is minor overlap between search and list, but the descriptions and intended use cases make the boundary explicit.
All tools share the k4g_ prefix and use snake_case with a verb-first structure. k4g_flag_for_review and k4g_list_pending_review deviate slightly from the direct verb_noun pattern of the other two, but the convention is still clear and predictable.
Four tools is a well-scoped set for an application triage server: search, detail view, pending queue, and flagging for discussion. Each tool covers a distinct step in the triage workflow without unnecessary bloat.
The read and flag workflows are covered, but there is no tool to mark an application as reviewed, assign a reviewer, or advance an application to the next pipeline stage. This creates a dead end where triage can only move applications into a discussion state, not out of it.