Skip to main content
Glama
Sign In
mcp-judge

mcp-judge

by Bum-Boo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

judge_ingest

Classifies an incoming message into a bounded action category and records its triage decision for routing to dismissal, notification, or calendar registration.

Instructions

Classify one incoming message and record its triage decision.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>",
      "item_id": "<item_id>",
      "text": "<text>"
    },
    "name": "judge_ingest"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
sourceYes
contextNo
item_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full behavioral disclosure burden. It reveals that the tool records a triage decision, implying a mutation, but does not describe side effects, idempotency, duplicate handling, permissions, or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no redundant or filler content. Every part of the sentence contributes to stating the tool's action and result.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described in detail. However, for a four-parameter mutation tool with no annotations and no parameter descriptions, the description is too sparse to complete the agent's understanding of inputs and side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All four parameters have zero schema description coverage, and the description does not explain what 'source', 'item_id', 'text', or 'context' mean or how they should be provided. It only generally refers to an 'incoming message', adding no meaningful parameter-level guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verbs ('Classify', 'record') and identifies the resource ('one incoming message') and output ('triage decision'). It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools like judge_pending or judge_get.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives such as judge_get, judge_pending, or judge_health. It implies ingestion of incoming messages but provides no exclusions, prerequisites, or conditions for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools