Skip to main content
Glama

Content Intake Triage

by io.github.Wxt-ai
OverviewDiscussionsAdmin

Server Details

Triage a workspace content item

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over 37 days
Last Tested
Transport
Streamable HTTP
URL

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion with other tools. The tool's purpose is clearly described.

Naming Consistency5/5

A single tool trivially follows a consistent naming pattern. The name uses a clear verb_noun structure (classify_content_sensitivity).

Tool Count1/5

A single tool for a server called 'Content Intake Triage' is extremely minimal. Triage typically involves multiple operations (categorize, route, prioritize), and one classification tool is insufficient for the implied scope.

Completeness1/5

The tool only classifies content sensitivity, but a triage system would likely need to create review tasks, assign reviewers, or update status. There are obvious gaps for basic triage workflows.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedclassify_content_sensitivity

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources