Skip to main content
Glama
Sign In
openport

openport

by theodorexli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_skill

Create or update a named skill, choosing replace or append mode for its body. Use it before session setup for installation or recovery, then reload the skill after editing.

Instructions

Create or update a skill. Available before session setup for installation/recovery; editing a loaded skill requires clients to reload it.

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": {
      "skill": "<skill>",
      "body": "<body>"
    },
    "name": "update_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
modeNo
skillYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It usefully discloses a lifecycle constraint — usable before session setup, and clients must reload after editing a loaded skill. It omits what happens to existing content, whether operations are reversible, and any error conditions.

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?

Two short sentences with no filler, and the core action is front-loaded. The second sentence packs two distinct constraints (availability window, reload requirement) a bit densely but without waste.

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?

For a mutation tool with no annotations, no output schema, and zero parameter documentation, the description is thin. An agent still cannot tell what a skill body looks like, what the mode enum does, or what the result of the call is.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters. The description never explains what 'skill' identifies, what 'body' contains, or how the 'replace' vs 'append' modes differ, even though the enum choice materially changes behavior.

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 and resource ('Create or update a skill'), which is clear enough for an agent to know what the tool does. However, it never distinguishes itself from the sibling get_skill or explains why it covers both create and update paths.

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 sentence about availability 'before session setup for installation/recovery' implies a usage window, and the reload caveat hints at a constraint when editing loaded skills. But it never explicitly says when to choose this over get_skill or learn_workflow, nor what conditions make it unusable.

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