Skip to main content
Glama
Sign In
openport

openport

by theodorexli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_context

Discover available memory scopes or load scoped context and session handoffs, with must-load and shared scopes included automatically; returns IDs, kinds, and timestamps.

Instructions

Discover available scopes with get_context(), or load memory by scope/scopes (must-load and shared scopes auto-included). A scope shorthand allows one local. An explicit scopes list may name several locals. The index returns IDs, kinds, and timestamps only. Prefer start_session once you know the local.

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": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoSingle scope id shorthand (must-load auto-included). Prefer scopes=.
scopesNoScope ids to load (e.g. [_important, _protected, desk]). Must-load always merged in.
include_globalNoOn scoped loads, also include _global (default false).
include_sessionNoOn scoped loads, also include _session handoffs (recommended true at session start).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It usefully notes that must-load/shared scopes are auto-included and that the index returns only IDs, kinds, and timestamps, which is real behavioral content. It omits safety profile, side effects, and anything about permissions or the loaded-memory payload beyond the index.

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?

Dense but front-loaded with the primary verb and resource. No filler sentences, and the start_session pointer closes cleanly. A couple of clauses ('A scope shorthand allows one local') are terse to the point of mild obscurity but still economical.

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

Completeness4/5

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

No output schema exists, yet the description explains what the index returns (IDs, kinds, timestamps) and how scopes are merged in. For a no-annotation, no-output-schema read tool, this covers the essentials; the missing piece is a clearer when-to-use statement for the two modes.

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%, so the schema already documents all four parameters. The description adds modest clarification—shorthand allows one local, scopes list may name several, must-load auto-included—but largely restates what the schema descriptions already convey. Baseline 3 fits.

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 two specific modes: 'Discover available scopes' and 'load memory by scope/scopes', with a concrete return profile ('IDs, kinds, and timestamps only'). It distinguishes itself from start_session by routing to it ('Prefer start_session once you know the local'). The dual discover/load framing is slightly ambiguous but still legible against siblings.

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?

Provides a routing hint ('Prefer start_session once you know the local') and differentiates the shorthand vs list forms. However, it doesn't explicitly state when to choose the discovery mode versus a scoped load, leaving the core use decision partly implicit.

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