Skip to main content
Glama
enesjakozh
CheMiguel23

MemoryMesh

by CheMiguel23
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

read_graph

Access and interpret the full knowledge graph stored in the MemoryMesh MCP server to retrieve structured data and insights efficiently.

Instructions

Read the entire knowledge graph

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/integration/tools/handlers/SearchToolHandler.ts:13-18 (handler)
    The handler function for the 'read_graph' tool, which retrieves the entire knowledge graph via the knowledgeGraphManager and formats the response.
    case "read_graph":
    const graph = await this.knowledgeGraphManager.readGraph();
    return formatToolResponse({
        data: graph,
        actionTaken: "Read complete knowledge graph"
    });
  • src/integration/tools/registry/staticTools.ts:178-185 (registration)
    Registration of the 'read_graph' tool including its name, description, and empty input schema.
    {
    name: "read_graph",
    description: "Read the entire knowledge graph",
    inputSchema: {
        type: "object",
        properties: {},
    },
},
  • src/integration/tools/registry/staticTools.ts:181-184 (schema)
    Input schema definition for the 'read_graph' tool, which requires no parameters.
    inputSchema: {
    type: "object",
    properties: {},
},
  • src/integration/tools/handlers/ToolHandlerFactory.ts:46-47 (registration)
    Routing logic in ToolHandlerFactory that directs 'read_graph' tool calls to the SearchToolHandler.
    if (toolName.match(/^(read_graph|search_nodes|open_nodes)$/)) {
    return this.searchHandler;

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose whether this is a safe read operation, potential performance impacts of reading the 'entire' graph, authentication needs, rate limits, or what the return format looks like. 'Read' implies non-destructive, but this isn't explicitly confirmed.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it immediately clear. Every word earns its place by specifying 'entire' to differentiate scope.

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

Completeness2/5

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

Given the complexity of reading an entire knowledge graph, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'entire' entails (e.g., all nodes/edges), potential size limitations, return format, or error conditions. For a tool with significant scope, more context is needed.

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 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. Baseline is 4 for zero parameters, as the description correctly avoids unnecessary parameter explanation.

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?

The description 'Read the entire knowledge graph' clearly states the action (read) and resource (knowledge graph), making the purpose immediately understandable. It distinguishes from siblings like 'search_nodes' or 'open_nodes' by specifying 'entire' scope. However, it doesn't explicitly contrast with all siblings, keeping it at 4 rather than 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'search_nodes' or 'open_nodes'. It doesn't mention prerequisites, performance considerations for reading the 'entire' graph, or any exclusions. The agent must infer usage from the name and description alone.

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

Related 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/CheMiguel23/MemoryMesh'

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