Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_agent_context

Read-only

Retrieve stored agent memory at session start to recall learned printer, material, and print outcome details. Filter by printer or scope; expired entries are excluded automatically.

Instructions

Retrieve all stored agent memory for context.

Call this at the start of a session to recall what you've learned
about printers, materials, and past print outcomes.  Expired entries
are automatically filtered out.  Each entry includes a ``version``
field showing how many times it has been updated.

Args:
    printer_name: If provided, retrieves printer-specific memory.
    scope: Filter by scope (e.g., ``"global"``, ``"fleet"``).

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": "get_agent_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoFilter by scope (e.g., ``"global"``, ``"fleet"``).
printer_nameNoIf provided, retrieves printer-specific memory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / printer_name / description
      Added value: +"If provided, retrieves printer-specific memory."
    • addedInput schema / properties / scope / description
      Added value: +"Filter by scope (e.g., ``\"global\"``, ``\"fleet\"``)."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / printer_name / default
      Removed value: -null
    • removedInput schema / properties / scope / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: expired entries are auto-filtered and each entry carries a 'version' count of updates, which an agent could not infer from structured fields.

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?

Front-loaded with purpose, then session-timing guidance, then behavior notes; nothing is buried. The Args section duplicates schema descriptions and slightly inflates length, which keeps it from a 5.

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 2-optional-parameter read tool with no output schema, the description covers what is returned (entries with a version field), what is excluded (expired entries), and when to call it. Minor gap: no indication of result size or ordering when neither filter is supplied.

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 description coverage is 100%, so the baseline is 3. The Args block restates the schema text almost verbatim ('If provided, retrieves printer-specific memory', 'Filter by scope'), adding no format hints, enum values, or interaction rules between the two filters.

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 ('Retrieve all stored agent memory') with explicit scope ('all stored'), which cleanly separates it from the write-side siblings save_agent_note, delete_agent_note, and clean_agent_memory without needing to name them.

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?

Gives a concrete trigger: 'Call this at the start of a session to recall what you've learned about printers, materials, and past print outcomes.' That is clear when-to-use guidance, but there is no when-not to use it and no explicit pointer to save_agent_note or clean_agent_memory as the 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