Skip to main content
Glama
Sign In
openport

openport

by theodorexli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_skill

Read an instruction skill by ID or list all available skills using "*" to access scoped agent guidance from the openport memory server.

Instructions

Read an instruction skill by id, or list with skill="*".

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>"
    },
    "name": "get_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. 'Read' implies non-mutating behavior, but nothing is said about what happens when the id is unknown, whether listing returns full skill bodies or just names, or any auth constraints.

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?

One tight sentence with the primary mode front-loaded and the list variant attached. The literal `skill="*"` quoting is slightly awkward but not wasteful.

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?

This is a simple one-parameter read tool with no output schema, so the burden is light. Still, the id format and the distinction between single-read and list return shapes are left unstated, which an agent needs before calling.

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 coverage is 0% (the single 'skill' string parameter has no description), and the description compensates partially by revealing the '*' wildcard value for listing. It still never explains what a valid id looks like or what other values are accepted.

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 the verb (read) and resource (instruction skill) plus the dual mode (fetch by id vs. list with '*'), which separates it from update_skill. It does not explicitly contrast with learn_workflow, but the resource noun does most of the distinguishing work.

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 description implies the two calling modes (id lookup vs. wildcard listing) but never says when to prefer learn_workflow over reading a skill directly, nor any prerequisites. Adequate implied usage, no explicit alternatives.

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