Skip to main content
Glama
Sign In
openport

openport

by theodorexli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

start_session

Begin a work session to unlock a skill, load required context and session handoffs, and return the next action to take.

Instructions

GATE — first tool every work session. Unlocks a skill, loads must-load + one local + _session, returns next_action. Default skill: bootstrap (seed) or resume-work. Prefer this over bare get_context.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoAlways return full skill body
localNoLocal scope id (default desk)
skillNoOverride skill id (default: bootstrap if seed, else resume-work)
knownHashNoPrior skillHash — if it matches, skill body is omitted
include_globalNoAlso include _global

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the loading behavior, the skill-body suppression via knownHash, and that next_action is returned, but it never says whether calling it twice is safe, whether session state is overwritten, or what the agent is expected to do with next_action.

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?

Three short sentences, front-loaded with the gating instruction and the sibling preference last. Dense and largely waste-free, though the compressed notation ('must-load + one local + _session') costs clarity for brevity.

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?

No output schema and no annotations, so the description has to explain the return, and it only names next_action without describing its shape or the agent's expected follow-up. For a session-initialization gate with five parameters, the behavioral picture is adequate but thin.

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 100% with five well-described optional parameters, so the schema does the heavy lifting. The description only adds the default-skill rule (bootstrap if seed, else resume-work), which the schema's skill description also states.

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?

The opening 'GATE — first tool every work session' plus 'Unlocks a skill, loads must-load + one local + _session, returns next_action' gives a specific verb and a concrete list of what it loads. The idiosyncratic vocabulary (must-load, _session, next_action) is unexplained, so an agent gets the gist but not the mechanics.

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

Usage Guidelines4/5

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

'first tool every work session' is an explicit trigger condition, and 'Prefer this over bare get_context' names a sibling and routes away from it. Defaults for the skill parameter are spelled out, but no when-not condition or note about repeated invocation is given.

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