Skip to main content
Glama
vjsr007
by vjsr007

graph-stats

Analyze node and edge counts in a graph store to track relationships and structures within indexed notes, enabling insights into knowledge graphs and semantic connections.

Instructions

Get counts of nodes and edges in the graph store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'graph-stats' tool call. Validates input schema and invokes graph.stats() to retrieve node and edge counts, returning JSON.
    case 'graph-stats': {
      GraphStatsSchema.parse(args ?? {});
      const res = graph.stats();
      return { content: [{ type: 'text', text: JSON.stringify(res) }] };
    }
  • src/mcp.ts:184-188 (registration)
    MCP tool registration defining name, description, and input schema (empty object) for 'graph-stats'.
    {
      name: 'graph-stats',
      description: 'Get counts of nodes and edges in the graph store.',
      inputSchema: { type: 'object', properties: {} },
    },
  • Zod schema for GraphStats input validation (empty schema since tool takes no parameters).
    export const GraphStatsSchema = z.object({});
    export type GraphStatsInput = z.infer<typeof GraphStatsSchema>;
  • Core stats() implementation in SqliteGraphStore class, executing SQL COUNT queries on graph_nodes and graph_edges tables.
    stats(): { nodes: number; edges: number } {
      const n = (this.db.prepare(`SELECT COUNT(*) as c FROM graph_nodes`).get() as any).c as number;
      const e = (this.db.prepare(`SELECT COUNT(*) as c FROM graph_edges`).get() as any).c as number;
      return { nodes: n, edges: e };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'gets' counts, implying a read-only operation, but doesn't specify if it requires permissions, has rate limits, returns real-time or cached data, or what the output format looks like. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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, clear sentence that directly states the tool's function without any fluff or redundant information. It is front-loaded and appropriately sized for a zero-parameter tool, making it easy for an agent to parse and understand quickly.

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 tool's simplicity (0 parameters, no output schema), the description is minimal but adequate for the basic function. However, with no annotations and no output schema, it lacks details on behavioral aspects like permissions, rate limits, or return format, which could be important for an agent to use it correctly in a broader context.

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 the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, as there are none to document. It efficiently states what the tool does without unnecessary parameter explanations, aligning well with the schema's completeness.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('counts of nodes and edges in the graph store'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'graph-neighbors' or 'graph-path', which might also provide graph-related information but with different scopes or outputs.

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. It doesn't mention any prerequisites, context for usage, or comparisons to sibling tools such as 'graph-neighbors' for neighbor counts or 'index-health' for system metrics, leaving the agent to infer usage based on the name 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

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/vjsr007/mcp-index-notes'

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