Skip to main content
Glama
Sign In
Edition Intelligence Platform

Edition Intelligence Platform

by hiroshic9-png
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

memory_context

Read-onlyIdempotent

Retrieve a summary of current session facts and agreements to maintain agent context across interactions.

Instructions

現在のセッション状態（有効な事実・合意事項のサマリー）を取得します。エージェントのプロンプトに注入して文脈を維持するために使います。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idNoセッションID（省略で全体）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds context by specifying what data is retrieved (session state summary), which is valuable beyond annotations.

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 concise sentences in Japanese, front-loaded with the tool's action first, then use case. Every sentence adds value with no 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?

The description explains the return value (summary of facts/agreements) and its intended use. It lacks explicit differentiation from sibling memory tools, but overall adequate for a simple retrieval tool with no output schema.

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% and the description does not add extra meaning to the optional session_id parameter. Baseline of 3 is appropriate as the schema already documents it fully.

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 retrieves the current session state summary of facts and agreements. However, it does not explicitly differentiate from sibling tools like memory_facts or memory_recall, though the resource is distinct.

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?

The description explicitly mentions using it to inject into the agent's prompt for maintaining context, providing clear usage context. It does not mention when not to use or specify alternatives.

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

Deploy Server

Other Tools