Skip to main content
Glama

graph_stats

Retrieve counts of entities, edges, and mentions in the knowledge graph to assess its size and content.

Instructions

How many entities, edges and mentions the graph holds.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses what is reported (counts of entities, edges, mentions), which implicitly frames it as a read-only, side-effect-free operation, but it never explicitly says it is read-only or cheap, nor whether the counts span the entire graph or some scoped subset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler, and the key information (the three counted metrics) appears immediately. It is a sentence fragment rather than a structured statement, which slightly weakens front-loading of intent.

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?

For a zero-parameter, read-only statistics tool with no annotations and no output schema, the description covers the essentials by naming the three values returned. The exact return shape (flat object vs. nested per-type breakdown) and any scoping of the counts are left unspecified, which is a minor gap.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies a parameterless aggregate call.

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 names the specific resource (the graph) and the exact metrics returned (entity, edge and mention counts). It is a noun phrase rather than a verb-first statement, but an agent can immediately tell this is the only aggregate-statistics tool among siblings like search_brain, query_notes and find_entity.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. Usage is only implied: the phrase 'the graph holds' signals a whole-graph overview as opposed to filtered lookups, which is enough for an agent to infer, but nothing is stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.