Skip to main content
Glama
Sign In
Engram

Engram

by staticroostermedia-arch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

mcp_engram_get_geosphere_frame

Retrieve the current Geosphere frame (origin, step count, active location, lens state) for audit, reproducibility, and lawfulness checks.

Instructions

WS3-B: Return the currently active Geosphere frame state (origin, frame_step counter, active_location summary). Used for audit, reproducibility checks, and lawfulness verification. Includes whether a lens is active.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0-beta.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool returns the current frame state including a lens active flag, implying no side effects. It does not detail authorization needs or rate limits, but for a read-only getter, this is adequate.

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 with no wasted words. Information is front-loaded.

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?

Given no parameters and no output schema, the description fully explains what the tool returns and its purpose. It is complete for a simple getter tool.

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?

The tool has no parameters, so schema coverage is 100%. Baseline is 4. The description adds no param details, but none are needed.

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 the tool returns the currently active Geosphere frame state with specific fields (origin, frame_step counter, active_location summary) and mentions use cases like audit and verification. It distinguishes from siblings like mcp_engram_set_geosphere_frame and mcp_engram_clear_geosphere_frame by focusing on retrieval.

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 states usage for audit, reproducibility checks, and lawfulness verification. It does not explicitly list when not to use it or alternatives, but the context is sufficient for 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