Skip to main content
Glama
phocinae-mcp

phocinae-mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PHOCINAE_MCP_HTTP_PORTNoPort for the Streamable HTTP transport, can be used instead of the --port command line switch
PHOCINAE_MCP_TRANSPORTNoTransport to use for the MCP server, can be used instead of the --transport command line switch (stdio|http)

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
gateA

何时使用:需要判定一条 shell 命令能否执行时——代码代理要跑命令、批处理要校验、人工要复核灰区命令,都用 gate 逐条判定。何时不使用:不要用它判定非 shell 操作(文件读写、HTTP 调用);不要把多条命令拼成一条字符串绕过判定;宿主已有内置审批机制时不要重复叠加。返回 decision ∈ allow|deny|ask 与 layer/reason;ask 时结果携带人工确认交互(MCP 2026-07-28 elicitation)或明示需人工复核;服务不可用 fail-closed 返回 deny。

classifyA

何时使用:需要把一段状态/上下文归入若干已知标签之一(意图分类、类型识别)时。何时不使用:标签未知或不固定时(改走 route 或让模型自由作答);需要对同一对象打多重分数时(用 score)。返回 choice=选项下标(0 起)、label、置信度;服务不可用返回明确错误。

routeA

何时使用:有确定的候选工具/处理器清单、需要从中挑出最合适的一个来服务请求时。何时不使用:候选清单不固定或用户已直接指定工具时(尊重用户指定,不重复路由);要评估每个候选的质量而非挑选时(用 score 逐个打分)。返回 choice=下标、tool=选中的工具名;服务不可用返回明确错误。

scoreA

何时使用:需要按 criteria 给 state 打 2–10 分(风险、质量、适配度等)时。何时不使用:需要分类(用 classify)、多选一(用 route 或 gate)、或分数语义与 2–10 量纲不符时。返回 score ∈ [2, 10] 与 range;服务不可用或应答越界返回明确错误。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a fundamentally different decision shape: gate = command allow/deny/ask, classify = pick one known label, route = pick one tool from a fixed candidate list, score = numeric 2–10 rating. The descriptions explicitly state when NOT to use each tool and cross-reference the alternatives (e.g. 'use route instead of classify when labels are unknown'; 'use score to rate each candidate'), which eliminates the usual classify/route/score overlap.

Naming Consistency4/5

All four names are single lowercase English words with no camelCase/snake_case mixing, which is highly predictable. The only minor deviation is that gate reads as a noun/resource while classify, route, and score are verbs, but the concise one-word convention is still uniform.

Tool Count5/5

Four tools is well within the ideal 3–15 range and each corresponds to a distinct decision primitive (permit, categorize, select, rate). Nothing feels padded or missing at the count level; the surface is tightly scoped to a decision/judgment layer.

Completeness4/5

The server covers the core judgment operations—ternary gating, closed-set classification, single-choice routing, and bounded scoring—with explicit fail-closed/error behavior, so no major workflow dead-ends. Minor gaps exist around batch/multi-item evaluation and combined multi-step decisions, but agents can chain the four tools to work around these.

Maintenance

ActivityMaintained
ResponsivenessOutdated data