Skip to main content
Glama
Sign In
selfos-mcp

selfos-mcp

by AmineBenaceur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_context

Read-only

Load today's date, user preferences and identity, active goals with pace and check-in status, habits, upcoming birthdays, and vault file list to initialize coaching context.

Instructions

Call first. Returns today's date, the user's preferences and identity, active/paused goals with pace and check-in status, habits, upcoming birthdays, and a list of all vault files.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish that this is a safe read-only, non-destructive, closed-world operation. The description adds meaningful behavioral context by enumerating exactly what context is returned, including preferences, identity, pace/check-in status, and vault files, which is important since no output schema is provided.

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?

The description is compact and front-loaded with the key instruction "Call first." The return-content list is dense but entirely relevant for an initial context-loading tool.

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

Completeness5/5

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

With zero parameters, no output schema, and read-only annotations, the description carries the burden of explaining return contents and does so comprehensively. It covers all major categories an agent needs before deciding or acting.

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

Parameters4/5

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

The tool has zero parameters, so there is no parameter semantics to explain. The baseline for zero-parameter tools is 4, and the description does not introduce any parameter ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: it returns the user's current context, including date, identity/preferences, goals, habits, birthdays, and vault files. Its "Call first" framing and aggregate scope distinguish it from siblings like list_goals, list_habits, and upcoming_birthdays, which provide narrower views.

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?

It explicitly says "Call first," giving clear initial-use guidance. However, it does not name when not to use it or explicitly recommend the narrower sibling tools for follow-up queries, so full alternative guidance is absent.

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