Skip to main content
Glama
Sign In
mcp-flutter-apk-injector

mcp-flutter-apk-injector

by MarwanDevSpace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Retrieve Hermes+ agent context and session memory

get_agent_context
Read-onlyIdempotent

Retrieve the active reverse-engineering session context, including persona, skill sheets, pipeline telemetry, and memory snapshot. Use it at workflow start to assess pipeline status before modifications.

Instructions

Retrieve the Hermes+ reverse-engineering persona, loaded skill sheets, pipeline telemetry, and complete active session memory snapshot. This operation is read-only, non-mutating, and requires no authentication; omitting sessionId returns the active singleton session state without error. Use it at the start of an engineering workflow or to inspect overall pipeline status; use query_memory_graph for targeted keyword lookups or update_agent_memory to persist modifications.

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
sessionIdNoOptional session ID to fetch context for. If omitted, the default active singleton session state is retrieved

Output Schema

NameRequiredDescriptionDefault
skillsYesAvailable agent skill sheets.
personaYesHermes+ identity and engineering principles.
sessionMemoryYesActive session memory snapshot including target metadata, patch logs, and telemetry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.4
    • changedInput schema / properties / sessionId / description
      Previous value: -"Optional session ID to fetch context for"New value: +"Optional session ID to fetch context for. If omitted, the default active singleton session state is retrieved"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "persona": {
+      "additionalProperties": false,
+      "description": "Hermes+ identity and engineering principles.",
+      "properties": {
+        "name": {
+          "description": "Agent persona name.",
+          "type": "string"
+        },
+        "operationalRules": {
+          "description": "System and reverse engineering operational rules.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "title": {
+          "description": "Agent persona professional title.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "title",
+        "operationalRules"
+      ],
+      "type": "object"
+    },
+    "sessionMemory": {
+      "additionalProperties": {},
+      "description": "Active session memory snapshot including target metadata, patch logs, and telemetry.",
+      "type": "object"
+    },
+    "skills": {
+      "description": "Available agent skill sheets.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "description": {
+            "description": "Loaded skill operational capability description.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Loaded skill identifier.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "persona",
+    "skills",
+    "sessionMemory"
+  ],
+  "type": "object"
+}
  2. Addedv0.1.3

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds crucial context: requires no authentication, and omitting sessionId returns the active singleton session without error. This goes beyond the structured data and informs the agent about auth and default behavior.

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?

The description is two sentences, front-loaded with the primary purpose and then usage guidance. It is efficient, with no filler or redundant phrasing.

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?

With an output schema present, the description needn't detail return format. The tool is simple (one optional param, read-only), and the description covers purpose, usage, auth, and default behavior. Nothing critical is missing for an agent to call it correctly.

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?

There is only one optional parameter with 100% schema description coverage. The schema already explains that omission returns the default active singleton session. The description repeats this in behavioral transparency but doesn't add new parameter-specific meaning beyond the schema, so a baseline 3 is appropriate.

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?

The description clearly states a specific verb ('Retrieve') and resource (Hermes+ persona, skill sheets, pipeline telemetry, session memory snapshot). It also names siblings (query_memory_graph, update_agent_memory) for differentiation, so an agent can immediately tell this from the other memory tools.

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 states when to use (start of engineering workflow, inspect pipeline status) and when not (use query_memory_graph for targeted lookups, update_agent_memory for persistence). This is clear, actionable guidance that reduces mis-selection.

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