Skip to main content
Glama
sequico

server-noonien

Official
by sequico
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Read Graph

read_graph
Read-onlyIdempotent

Read the knowledge graph or a page of it in name order. Use optional limit and offset to skip entities and return a slice.

Instructions

Read the knowledge graph, or a page of it: the optional limit and offset take a slice of the entities in name order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoThe most entities to return; omit for all of them
offsetNoHow many entities to skip before the page; omit for none

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
entitiesYes
relationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "The most entities to return; omit for all of them",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "How many entities to skip before the page; omit for none",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv1.0.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds a genuinely useful behavioral fact beyond the annotations: entities are returned in name order, which is essential to know for offset pagination to be stable and meaningful.

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 dense sentence that front-loads the core action and appends the pagination detail after a colon. No filler, and the most important information comes first.

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 an output schema present the description need not explain return values, and the annotations carry the safety profile, so the only real gap was ordering — which it fills. A note on graph size or pagination expectations would have made it fully complete, but nothing essential is missing.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns above that by supplying the ordering semantics (name order) that the schema descriptions omit — without that, an agent cannot reason about what an offset actually skips over. It still doesn't state whether offsets are 0-based beyond what the schema says.

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 gives a specific verb and resource ("Read the knowledge graph") and explains the pagination slice, so the purpose is unambiguous. It does not, however, distinguish itself from siblings like search_nodes or open_nodes, which an agent could plausibly confuse with a full-graph read.

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?

Usage is implied rather than stated: the mention of limit/offset signals this is the bulk-read/pagination path, and unlike search_nodes there is no filtering. But there is no explicit when-to-use-this-vs-alternatives guidance or exclusion naming a sibling, so the agent must infer routing.

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