Skip to main content
Glama

UseMyContext.ai

by io.github.usemycontext

Your profile

profile
Read-only

Return the user's compiled personal context - a compact structured summary of who they are, synthesized from their accepted facts. Call it at the start of any conversation that involves the user personally, to ground who they are. This is ALSO the tool that sets a user up with UseMyContext: call it when they say 'set me up with UseMyContext', 'get me started', 'get to know me', 'onboard me', or otherwise ask you to learn about them. On a brand-new or empty profile the reply carries the setup instructions to follow; on an established one it carries their context. Do not reach for list_profiles for any of that - it only lists each profile's name, @handle, and privacy status. No file content. Read-only; nothing is written, so it is safe to call. Also reports the profile's privacy status (private, shared, network, public, or org) so you can describe it correctly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleNoOptional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given. Honored only for an account-wide connection; a single-project connection is already scoped and ignores it. A handle that is not one of the user's own profiles is refused outright, never quietly swapped for another profile. To read context someone ELSE shared with the user or published, use shared_context instead.
projectIdNoOptional: which of the user's profiles (projects) to read - a projectId from list_profiles. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextYesThe user's compiled personal context. When no current compilation exists, their raw accepted facts serialized as JSON.
privacyNoA short human-readable explanation of who can read this profile, matching the visibility value.
visibilityNoThe privacy status of this project's profile. Report it as-is; do not assume a profile is public.
profileStateNoWhich shape `context` is: 'current' (the compiled composite), 'stale' (raw facts - no current compilation), or 'empty' (the onboarding guidance for an empty account).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedOutput schema / properties / profileState
      Added value: +{
+  "description": "Which shape `context` is: 'current' (the compiled composite), 'stale' (raw facts - no current compilation), or 'empty' (the onboarding guidance for an empty account).",
+  "enum": [
+    "current",
+    "stale",
+    "empty"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / handle
      Added value: +{
+  "description": "Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given. Honored only for an account-wide connection; a single-project connection is already scoped and ignores it. A handle that is not one of the user's own profiles is refused outright, never quietly swapped for another profile. To read context someone ELSE shared with the user or published, use shared_context instead.",
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "Optional: which of the user's profiles (projects) to read - a projectId from list_profiles. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this.",
+  "type": "string"
+}
    • addedOutput schema / properties / privacy
      Added value: +{
+  "description": "A short human-readable explanation of who can read this profile, matching the visibility value.",
+  "type": "string"
+}
    • addedOutput schema / properties / visibility
      Added value: +{
+  "description": "The privacy status of this project's profile. Report it as-is; do not assume a profile is public.",
+  "enum": [
+    "private",
+    "shared",
+    "network",
+    "public",
+    "org"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses key behaviors beyond the readOnlyHint annotation: it is read-only and safe to call, returns setup instructions on an empty profile versus context on an established one, contains no file content, and reports privacy status. This adds meaningful operational context without contradicting the annotations.

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?

The description is longer than average but every section earns its place: core purpose, when to call, onboarding triggers, behavior on empty profiles, sibling differentiation, safety, and privacy output. It is front-loaded with the main verb and resource, and the additional length is justified by the tool's dual-purpose nature.

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?

Despite the tool's dual use and subtle account-wide vs single-project scoping nuance, the description covers usage timing, alternative tools, safety, empty-profile behavior, and output highlights. The output schema exists, so return-value detail does not need to be repeated. Nothing essential for correct invocation is missing.

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 input schema already fully documents both handle and projectId, including precedence, scoping behavior, and invalid-handle handling. The tool description itself adds no parameter-level information, but per the baseline for high schema coverage, a 3 is appropriate.

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 opens with a specific verb and resource: 'Return the user's compiled personal context - a compact structured summary of who they are.' It clearly distinguishes this from siblings like list_profiles ('it only lists each profile's name, @handle, and privacy status') and shared_context ('To read context someone ELSE shared... use shared_context instead'). Its dual role of onboarding is also explicitly stated.

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

Usage Guidelines5/5

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

Gives precise when-to-use guidance: 'Call it at the start of any conversation that involves the user personally' and identifies exact trigger phrases for onboarding ('set me up with UseMyContext', 'get me started', etc.). It also explicitly warns against the wrong alternative ('Do not reach for list_profiles for any of that') and directs users to shared_context for others' context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All UseMyContext.ai toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation3/5

Most tools have clear boundaries, but fetch/get_file and search/search_files are explicit aliases of each other, creating redundant purposes. account vs info and list_files vs search_files also require careful reading to tell apart, though the descriptions do provide guidance.

Naming Consistency3/5

The set mixes verb_noun names (list_files, query_table, suggest_update) with standalone nouns (account, info, profile) and bare verbs (fetch, search). The naming is readable and lowercase throughout, but the conventions are not uniform.

Tool Count5/5

Thirteen tools is a reasonable, well-scoped number for a personal-context and document-access server. The two alias pairs add some redundancy but do not make the set feel bloated.

Completeness4/5

The server covers the core read-only workflows: discovering files, searching semantically, querying tabular data, retrieving full documents, reading profiles, and accessing shared context. Direct profile editing or file mutations are intentionally out of scope for this read-only connection, and suggest_update provides the one sanctioned write path.

Resources