Skip to main content
Glama
Sign In
mcp-skylos

mcp-skylos

by duriantaco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Record a triage decision

learn_triage

Record whether a finding was accepted or dismissed so future triage suggestions learn from your decisions.

Instructions

Record whether a finding was accepted or dismissed so get_triage_suggestions can learn from it.

Writes the decision to the project's local Skylos state.

Requires SKYLOS_API_KEY: this tool returns an authentication error unless the MCP server is started with SKYLOS_API_KEY set. Without a key only analyze works (5 calls/day). The local CLI needs no key: skylos verify <file> and skylos agent install-hooks.

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": {
      "path": "<path>",
      "action_id": "<action_id>",
      "action": "<action>"
    },
    "name": "learn_triage"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesProject directory. A relative path resolves against the MCP server's working directory.
actionYes"accept" (real issue) or "dismiss" (false positive).
action_idYesThe finding's `fingerprint` from a scan result.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.49.0
    • addedInput schema / properties / action / description
      Added value: +"\"accept\" (real issue) or \"dismiss\" (false positive)."
    • addedInput schema / properties / action_id / description
      Added value: +"The finding's `fingerprint` from a scan result."
    • addedInput schema / properties / path / description
      Added value: +"Project directory. A relative path resolves against the MCP server's working directory."
  2. Addedv4.10.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description goes further: it discloses that the decision is persisted to the project's local Skylos state, that the call fails with an authentication error without SKYLOS_API_KEY, and the 5 calls/day quota on the unauthenticated path. That is exactly the failure-mode and persistence context annotations cannot carry.

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

Conciseness4/5

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

The purpose and feedback-loop rationale are front-loaded in the first sentence, followed by the write target and auth constraint. The trailing CLI sentence is slightly tangential for a description of this specific tool, but it earns its place by routing the agent when no key is available.

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

Completeness5/5

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

For a 3-required-parameter mutation tool with an output schema, the description covers purpose, when to use it, authentication requirements, failure behavior, persistence target, and alternatives. Return values are handled by the output schema, so nothing an agent needs to invoke it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100% – path, action, and action_id each have their own description, including the accept/dismiss enum values. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Record whether a finding was accepted or dismissed') and ties it to a named sibling, `get_triage_suggestions`, explaining the feedback loop. An agent can distinguish this from the other triage/scan siblings without opening a schema.

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

Usage Guidelines5/5

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

Explicit about when to call it (after accepting/dismissing a finding), the prerequisite (SKYLOS_API_KEY must be set or it errors), and the alternatives when the key is absent (only `analyze`, or the local CLI `skylos verify`/`skylos agent install-hooks`). This is genuine when/when-not guidance with named fallbacks.

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