Skip to main content
Glama

Metis — Get Context

get_context

Retrieve relevant prior information from Metis memory within a token budget, returning progressive detail as budget allows. Uses semantic and keyword search, filtered by time and agent.

Instructions

Recall relevant prior context within a token budget.

Progressive disclosure: returns more detail when budget allows.
  ≤ 500 tokens  → index only   (type + first 12 words per entry)
  ≤ 2000 tokens → preview      (type + first 40 words)
  >  2000 tokens → full         (complete content)

Combines semantic vector search (if fastembed available) with keyword
fallback, filtered to the last `days` days.

Args:
    query:        What you are looking for — natural language.
    budget_tokens: How many tokens you can spend on context (default 2000).
    agent_slug:   Restrict to a specific agent's observations (optional).
    days:         How far back to search (default 90 days).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo
queryYes
agent_slugNo
budget_tokensNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses progressive disclosure behavior, search method (semantic+keyword fallback), and time filtering. Without annotations, description carries burden; it covers key traits but omits side effects or permissions.

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?

Concise overall, uses bullet and list for clarity, front-loaded with main purpose. Minor redundancy in threshold examples could be trimmed but generally efficient.

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?

Fully explains behavior, input semantics, output format (progressive disclosure), and fallback logic. With output schema present, return values need no further detail.

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

Parameters5/5

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

Schema has 0% description coverage; description explains all 4 parameters in detail (natural language query, token budget, agent restriction, time window), adding significant meaning beyond schema.

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?

Clearly states verb 'Recall' and resource 'prior context within a token budget'. Unique progressive disclosure feature distinguishes it from sibling memory tools like search_memory or recall.

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?

Provides explicit context for token budget and progressive disclosure thresholds, but does not directly contrast with sibling tools or state when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server