Skip to main content
Glama
sumithr

sumo-qa

by sumithr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sumo_qa_install_external_skill

Installs a previewed external skill via the pinned Skills CLI, verifying the approved digest and user confirmation before writing.

Instructions

Install a previewed external skill through the pinned Skills CLI.

confirmed: the user wants the previewed payload; approved_digest: that preview's content_digest, which the payload must still match. elevated_trust: only when the user grants it for a mutable ref or an untrusted source. sumo-qa then asks the user itself (MCP elicitation) before writing; a host that cannot ask is refused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNocodex
scopeNoproject
skillYes
sourceNohttps://github.com/vercel-labs/skills
confirmedNo
elevated_trustNo
approved_digestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.76.0
    • addedInput schema / properties / approved_digest
      Added value: +{
+  "default": "",
+  "type": "string"
+}
    • addedInput schema / properties / elevated_trust
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
  2. First observedv0.42.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this as a non-readOnly, non-idempotent, open-world write. The description goes beyond them by disclosing the destructive-action gate: sumo-qa performs MCP elicitation with the user before writing and refuses hosts that cannot ask, plus the digest must still match the preview. This is meaningful safety context not present in structured fields.

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?

Front-loaded one-line purpose followed by a tight parameter glossary; every clause carries meaning. It is compact and well-organized, with only minor density in the elicitation sentence.

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

Completeness3/5

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

For a 7-parameter, non-idempotent write with no output schema, the description covers the approval gate and digest contract well but is silent on what installation actually writes, how scope/agent/source affect the outcome, and any reversibility (the rollback sibling is not referenced). Adequate but with clear gaps.

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 0% across 7 parameters, so the description must compensate. It explains confirmed, approved_digest, and elevated_trust clearly with semantics (e.g., approved_digest must equal the preview's content_digest), but leaves agent, scope, skill, and source undocumented beyond their names and defaults.

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?

States a specific verb (Install) and resource (external skill) plus the mechanism (pinned Skills CLI), and the qualifier 'previewed' implies the preview workflow. It stops short of naming sumo_qa_preview_external_skill explicitly, so sibling differentiation is by implication rather than by name.

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

Usage Guidelines3/5

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

The word 'previewed' and the digest-matching requirement imply that sumo_qa_preview_external_skill must run first, and the elevated_trust clause gives a clear when-to-set condition. However, no alternative tool is named and there is no explicit when-not-to-use guidance, so the routing is left to inference.

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