Skip to main content
Glama
agenticempire

axint

by agenticempire
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

axint.context.memory

Read-onlyIdempotent

Return compact operating memory for AI agents to reload after session restart or context compaction, keeping Axint's rules accessible without rereading full documentation.

Instructions

Return the compact Axint operating memory that agents should reload at new chat start, after context compaction, or after long coding drift. Use this to keep Axint top-of-mind without rereading the full docs. Use: use after compaction or session restart for compact operating rules; use context.docs for longer workflow docs. Inputs: cwd selects project memory; format changes rendering without changing content. Effects: read-only generated context; writes no files and uses no network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformNoTarget Apple platform, such as macOS, iOS, visionOS, or all.
projectNameNoProject name to include in the memory.
expectedVersionNoExpected Axint version to compare against axint.status.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
isErrorNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • changedInput schema / properties / expectedVersion / description
      Previous value: -"Expected Axint ve..."New value: +"Expected Axint version to compare against axint.status."
    • changedInput schema / properties / platform / description
      Previous value: -"Target Apple plat..."New value: +"Target Apple platform, such as macOS, iOS, visionOS, or all."
    • changedInput schema / properties / projectName / description
      Previous value: -"Project name to i..."New value: +"Project name to include in the memory."
  2. Changed5 schema fields changedv0.4.34
    • changedInput schema / properties / expectedVersion / description
      Previous value: -"Expected Axint version to compare against axint.status."New value: +"Expected Axint ve..."
    • changedInput schema / properties / platform / description
      Previous value: -"Target Apple platform, such as macOS, iOS, visionOS, or all."New value: +"Target Apple plat..."
    • changedInput schema / properties / projectName / description
      Previous value: -"Project name to include in the memory."New value: +"Project name to i..."
    • removedOutput schema / properties / isError / description
      Removed value: -"Whether Axint marked the tool response as an error."
    • removedOutput schema / properties / text / description
      Removed value: -"Primary Axint tool response text, matching the first text content block."
  3. Changed2 schema fields changedv0.4.28
    • changedInput schema / properties / expectedVersion / description
      Previous value: -"Expected Axint version to compare against..."New value: +"Expected Axint version to compare against axint.status."
    • changedInput schema / properties / platform / description
      Previous value: -"Target Apple platform, such as macOS, iOS,..."New value: +"Target Apple platform, such as macOS, iOS, visionOS, or all."
  4. Addedv0.4.26

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 and destructiveHint=false. The description adds that it is 'read-only generated context; writes no files and uses no network', reinforcing the safety profile. However, it does not detail potential side effects beyond annotations, so a 4 is appropriate.

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?

Description is front-loaded with purpose and usage guidance. It is succinct but contains some redundancy (e.g., restating the use with different words). Still, it efficiently conveys key information without excess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of output schema and annotations, the description adequately covers usage context and high-level behavior. However, the parameter mismatch reduces completeness; the description should align with the schema to provide a full picture.

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

Parameters2/5

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

Schema has three parameters (platform, projectName, expectedVersion) all described. However, the description mentions 'cwd' and 'format' as inputs that do not appear in the schema, causing confusion. It does not clarify the actual parameters beyond the schema, which already has 100% coverage. The description's extra information is misleading rather than helpful.

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?

Description clearly states the tool returns 'compact Axint operating memory' and specifies when to use (new chat start, compaction, long coding drift). It distinguishes from sibling axint.context.docs by noting different use cases (operating rules vs longer workflow docs).

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?

Explicitly tells when to use this tool ('after compaction or session restart') and provides a clear alternative ('use context.docs for longer workflow docs'). This helps the agent choose correctly.

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/agenticempire/axint'

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