Skip to main content
Glama

get_personal_context

Retrieves user-shared facts, preferences, goals, and principles relevant to a task, ranked by relevance, so you can tailor assistance without guessing.

Instructions

Get what the user shared about themselves (facts, preferences, goals, principles) that is relevant to a task, most relevant first. Only items the user marked as shared are returned. Requires the separate personal-context permission.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task": "<task>"
    },
    "name": "get_personal_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesWhat you are helping with, in a sentence (for example "Evaluate a job offer").
kindsNoOptional: only these kinds.
max_itemsNoMaximum items (default 8, maximum 12).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 must carry the behavioral load and does disclose real traits: results are relevance-ordered, only user-marked-shared items are returned, and a separate permission is required. It stops short of describing the response shape, behavior on an empty permission scope, or how permission failure surfaces.

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?

Three short sentences with zero waste: the capability and ordering come first, followed by the sharing filter and the permission prerequisite. Each sentence contributes new, actionable 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 simple three-parameter read tool with no output schema and no annotations, the definition covers what is returned (item kinds), ordering, filtering, and the access prerequisite. Missing only return-shape and failure-mode detail, which is minor at this complexity.

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 all three parameters (task, kinds, max_items) are already documented with an example and defaults. The description's phrase 'relevant to a task' and 'most relevant first' adds the useful hint that the task string drives ranking, but otherwise repeats rather than extends the schema.

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+resource: retrieving user-shared facts, preferences, goals, and principles scoped to a task, with relevance ordering called out. It is clearly distinct from person/meeting/file-oriented siblings, though it never names an alternative (e.g., get_person or ask_library) to deconflict explicitly.

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?

The task-scoping requirement implies when to call it (when personalization would help a specific task), and the 'separate personal-context permission' note flags a prerequisite. However, there is no explicit when-not guidance and no named alternative for retrieving user information a different way.

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