Skip to main content
Glama

context_now

Read-only

Get a snapshot of current memory context, including recent memories, stats, and audit activity, to quickly see what your agent knows right now.

Instructions

Get a snapshot of your current memory context.

Returns recent memories, stats, and audit activity — a quick overview of what your agent knows right now.

Returns: JSON string with context snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations provide readOnlyHint=true. The description adds specific behavioral details: returns recent memories, stats, and audit activity – extending beyond the annotation. No contradictions detected.

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?

Description is concise: two sentences plus a return note. Front-loaded with the core purpose. Every sentence adds value without redundancy.

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?

With no parameters and a readOnly annotation, the description is mostly complete. It explains the return value is a JSON string with snapshot details. Missing formal output schema, but context signals indicate one exists externally.

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?

No parameters exist, so schema coverage is effectively 100%. The description adds no parameter info (none needed). Baseline 4 for 0 parameters is appropriate.

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?

The description clearly states it gets a 'snapshot of your current memory context' with recent memories, stats, and audit activity. It distinguishes from siblings like 'recall' or 'list_memories' by emphasizing a quick overview, but does not explicitly name alternatives.

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 description implies it's for a quick overview of current memory context, but lacks explicit guidance on when to use this vs alternatives like 'memory_stats' or 'list_memories'. No when-not-to-use or prerequisites mentioned.

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/novyxlabs/novyx-mcp'

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