Skip to main content
Glama
Sign In
Cortex-MCP

Cortex-MCP

by codesphere-u
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_query_entity

Inspect an entity’s active facts, superseded history, related episodes, and K-hop ego-graph neighborhood to retrieve knowledge graph context and lineage.

Instructions

Inspect an entity's active facts, superseded historical facts, related episodes, and K-hop ego-graph neighborhood.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity_id": "<entity_id>"
    },
    "name": "memory_query_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_hopsNoMaximum hop distance for ego-graph traversal.
entity_idYesEntity ID to inspect.
include_supersededNoInclude historical facts superseded by newer decisions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does disclose the read-only nature via "Inspect" and enumerates the returned data categories (facts, superseded history, episodes, neighborhood), but says nothing about result size, pagination, or what happens when the entity is unknown or the graph is large.

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?

A single well-formed sentence that front-loads the resource and then lists return categories in a logical order. No filler, 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?

With no output schema and no annotations, the description compensates well by enumerating the four result categories an agent will receive. Remaining gaps are secondary: truncation/size behavior and error semantics for missing entities.

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 all three parameters are already documented. The description does tie max_hops to the ego-graph and include_superseded to superseded facts, adding a little conceptual meaning, but no extra syntax, bounds, or default rationale beyond the schema.

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?

Names a specific verb ("Inspect") and resource ("an entity") and enumerates exactly what is returned: active facts, superseded facts, episodes, and the K-hop ego-graph. That makes it clearly a read/inspection tool versus the mutation siblings (memory_upsert_fact, memory_record_episode), though no alternative is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word "Inspect" and the entity_id requirement imply the usage context (fetch an entity's surrounding context), but there is no explicit when-to-use, when-not, or pointer to memory_time_travel / memory_compile_context for adjacent needs. Guidance is inferred rather than stated.

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