Skip to main content
Glama

get_context

Read-onlyIdempotent

Retrieves recent project activity (last 24h by default) with event summaries, decisions, errors, and accumulated knowledge to show what changed lately.

Instructions

Get RECENT ACTIVITY for a project (last 24h by default): event stream with summaries, decisions, errors, plus accumulated project knowledge. Use it for "what changed lately"; get_project_knowledge returns the durable facts, recall searches memory for one fact.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoFilter by tags.
limitNoMax events to return (default 50).
sinceNoOnly events after this timestamp (RFC3339).
project_idYesUUID of the project whose recent activity to read (list_projects returns ids).
event_typesNoFilter by event types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID."New value: +"UUID of the project whose recent activity to read (list_projects returns ids)."
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by describing the return shape (event stream with summaries, decisions, errors, plus accumulated knowledge) and the default time window. It does not mention pagination limits beyond the schema's own limit param, so not a full 5.

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 dense sentences: the first front-loads the core purpose and payload contents, the second routes the agent to siblings. No filler, no repetition of the tool name.

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?

No output schema exists, and the description compensates by naming what the event stream contains and the default time window. Combined with full schema coverage and read-only annotations, an agent has everything needed to call it correctly and interpret the result.

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?

Schema coverage is 100%, so baseline is 3. The description earns above baseline by clarifying the default temporal window (last 24h), which explains how the optional `since` parameter interacts with the default behavior — a detail the schema does not spell out.

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?

States a specific verb and resource (get recent activity for a project) with an explicit scope and default window (last 24h), then lists what the payload contains (event stream with summaries, decisions, errors, plus accumulated project knowledge). An agent can distinguish it from get_project_knowledge and recall purely from this sentence.

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 a concrete selection rule ("Use it for 'what changed lately'") and names two alternatives with the exact conditions that favor them: get_project_knowledge for durable facts, recall for one fact. Both include-and-exclude guidance is present.

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