Skip to main content
Glama
Sign In
ContextOS

ContextOS

by aftabkh4n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

context

Returns a Markdown summary of workspace memories across current, weekly, or all scopes, so agents can retrieve details beyond the session-start summary.

Instructions

Read-only. Returns a Markdown summary of this workspace's memories. Use it when you need more than the summary injected at session start.

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

Input Schema

NameRequiredDescriptionDefault
scopeNocurrent (default): recent decisions, todos, skills and git state. week: memories from the last 7 days. all: every stored memory.current

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.5
    • changedInput schema / properties / scope / description
      Previous value: -"current, week, or all"New value: +"current (default): recent decisions, todos, skills and git state. week: memories from the last 7 days. all: every stored memory."
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose read-only semantics and the Markdown return format, which is worth credit, but says nothing about output size, truncation, cost, or how much memory is actually returned — significant for a tool whose output is dumped into context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero waste, safety stated first and the usage trigger second. Nothing could be removed without losing information.

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?

For a single-parameter read tool with fully documented schema and a stated return format, the definition covers what an agent needs to call it correctly. The missing piece is guidance on how this differs from `recall`, plus any sense of output volume.

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 100%, so the `scope` parameter and all three of its values are already documented in the schema. The description adds no further meaning about scope, so baseline 3 applies.

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: returns a Markdown summary of this workspace's memories, and frames it relative to the session-start summary. It does not distinguish itself from the closest sibling `recall`, so an agent comparing the two must infer the difference.

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?

Gives a clear positive trigger: use it when the injected session-start summary is insufficient. There is no explicit when-not guidance and no named alternative (e.g. `recall` for targeted lookups), so selection against siblings is left partly 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