Skip to main content
Glama
Sign In
littlebigbrains

@littlebigbrain/mcp

by littlebigbrains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

lbb_inspect

Read-only

Read exact graph facts, ontology and schema metadata, publication status, and complete entity records from a Little Big Brain knowledge graph, with paging and commit-pinned history.

Instructions

Read graph context and exact graph facts. Actions: guide, graphs, publication, ontology, ontology_conformance, schema, ontology_search, metadata, entity, ontology_suggestions. graphs works before bootstrap; ontology_suggestions lists the ontology change suggestions that wait for review (or were decided); fact_count is how many graph facts (triplets and entity property rows) accepting one commits, and identity_count how many identities it links. publication reports whether writes are queryable. ontology and schema return complete entries with page_size, section and cursor; follow next until absent. schema reads active native ontology/SHACL metadata without running validation. Query asserted RDF/OWL axioms separately with lbb_query. ontology_conformance serves the durable report referenced by the pinned published root. entity with iri, or version=records/1 and entity_id or entity_type+key, returns a complete exact-term record, separate assertions and snapshot from RDF. as_of_commit_seq pins retained history; schema-bound historical selection is currently unsupported. Oversized records fail rather than truncate. Omitting the new selectors preserves the native attributes/relationships view. Use lbb_query with SPARQL property paths for precise path selection.

Input Schema

NameRequiredDescriptionDefault
iriNoAuthoritative full RDF IRI; selects the lossless records/1 read.
keyNoStable key with entity_type, resolved from the activated schema at the read snapshot.
nameNo
as_ofNoUnsupported for entity; use as_of_commit_seq for a retained commit snapshot.
graphNoGraph to target; defaults to the connection's graph
limitNo
queryNoOntology concept, term, or relation to search
top_kNo
actionYesSelects the variant (one of: guide, ontology, ontology_conformance, schema, graphs, publication, ontology_search, metadata, ontology_suggestions, entity).
cursorNoOpaque lbb_inspect continuation. Repeat action and pass the returned next arguments; rejects changed metadata.
detailNoResponse detail level. Defaults to compact.
limitsNoLossless records/1 section bounds. Exceeding a bound refuses the read instead of truncating it.
statusNoOnly suggestions in this state; default all
sectionNoOptional top-level array to inspect, e.g. entity_type_defs, relation_defs, property_defs, classes, or relations. Omit to page through all sections.
versionNo
entity_idNoEntity id (hex); alternative to entity_type+name
page_sizeNoMaximum complete metadata entries per page; defaults to 50. Nested fields are never truncated; an oversized single entry returns serialized_json fragments to concatenate and parse.
consistencyNo
entity_typeNo
schema_revisionNoExpected opaque schema revision for a records/1 read.
as_of_commit_seqNoSnapshot pin: reproduce the node's attributes and relationships as of this commit_seq.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.16.0
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • addedInput schema / properties / as_of_commit_seq / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / consistency
      Added value: +{
+  "enum": [
+    "strong",
+    "eventual"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / iri
      Added value: +{
+  "description": "Authoritative full RDF IRI; selects the lossless records/1 read.",
+  "type": "string"
+}
    • addedInput schema / properties / key
      Added value: +{
+  "description": "Stable key with entity_type, resolved from the activated schema at the read snapshot.",
+  "type": "string"
+}
    • addedInput schema / properties / limits
      Added value: +{
+  "additionalProperties": false,
+  "description": "Lossless records/1 section bounds. Exceeding a bound refuses the read instead of truncating it.",
+  "properties": {
+    "assertion_statements": {
+      "exclusiveMinimum": 0,
+      "maximum": 10000,
+      "type": "integer"
+    },
+    "assertions": {
+      "exclusiveMinimum": 0,
+      "maximum": 100,
+      "type": "integer"
+    },
+    "incoming": {
+      "exclusiveMinimum": 0,
+      "maximum": 10000,
+      "type": "integer"
+    },
+    "outgoing": {
+      "exclusiveMinimum": 0,
+      "maximum": 10000,
+      "type": "integer"
+    },
+    "properties": {
+      "exclusiveMinimum": 0,
+      "maximum": 10000,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / schema_revision
      Added value: +{
+  "description": "Expected opaque schema revision for a records/1 read.",
+  "type": "string"
+}
    • addedInput schema / properties / top_k / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / version
      Added value: +{
+  "const": "records/1",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / as_of / description
      Previous value: -"Valid-time snapshot pin (RFC3339): reproduce the node as of this instant."New value: +"Unsupported for entity; use as_of_commit_seq for a retained commit snapshot."
  3. Changed4 schema fields changedv0.8.1
    • changedInput schema / properties / action / description
      Previous value: -"Selects the variant (one of: guide, ontology, ontology_conformance, schema, graphs, publication, ontology_search, metadata, entity)."New value: +"Selects the variant (one of: guide, ontology, ontology_conformance, schema, graphs, publication, ontology_search, metadata, ontology_suggestions, entity)."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "guide",
-  "ontology",
-  "ontology_conformance",
-  "schema",
-  "graphs",
-  "publication",
-  "ontology_search",
-  "metadata",
-  "entity"
-]New value: +[
+  "guide",
+  "ontology",
+  "ontology_conformance",
+  "schema",
+  "graphs",
+  "publication",
+  "ontology_search",
+  "metadata",
+  "ontology_suggestions",
+  "entity"
+]
    • addedInput schema / properties / limit
      Added value: +{
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Only suggestions in this state; default all",
+  "enum": [
+    "open",
+    "accepted",
+    "dismissed",
+    "superseded"
+  ],
+  "type": "string"
+}
  4. Changed8 schema fields changedv0.6.0
    • changedInput schema / properties / action / description
      Previous value: -"Selects the variant (one of: guide, ontology, ontology_conformance, schema, graphs, publication, ontology_search, metadata, entity, state, history, why, transitions)."New value: +"Selects the variant (one of: guide, ontology, ontology_conformance, schema, graphs, publication, ontology_search, metadata, entity)."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "guide",
-  "ontology",
-  "ontology_conformance",
-  "schema",
-  "graphs",
-  "publication",
-  "ontology_search",
-  "metadata",
-  "entity",
-  "state",
-  "history",
-  "why",
-  "transitions"
-]New value: +[
+  "guide",
+  "ontology",
+  "ontology_conformance",
+  "schema",
+  "graphs",
+  "publication",
+  "ontology_search",
+  "metadata",
+  "entity"
+]
    • changedInput schema / properties / as_of_commit_seq / description
      Previous value: -"Snapshot pin: reproduce the node (state, edges, history) as of this commit_seq."New value: +"Snapshot pin: reproduce the node's attributes and relationships as of this commit_seq."
    • removedInput schema / properties / relation
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / source_name
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / source_type
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / target_name
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / target_type
      Removed value: -{
-  "type": "string"
-}
  5. Changed1 schema field changedv0.5.2
    • removedInput schema / properties / branch
      Removed value: -{
-  "description": "Branch to target; defaults to the connection's branch",
-  "type": "string"
-}
  6. Changed5 schema fields changedv0.5.1
    • changedInput schema / properties / action / description
      Previous value: -"Selects the variant (one of: guide, ontology, ontology_conformance, schema, ontology_search, metadata, entity, state, history, why, transitions)."New value: +"Selects the variant (one of: guide, ontology, ontology_conformance, schema, graphs, publication, ontology_search, metadata, entity, state, history, why, transitions)."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "guide",
-  "ontology",
-  "ontology_conformance",
-  "schema",
-  "ontology_search",
-  "metadata",
-  "entity",
-  "state",
-  "history",
-  "why",
-  "transitions"
-]New value: +[
+  "guide",
+  "ontology",
+  "ontology_conformance",
+  "schema",
+  "graphs",
+  "publication",
+  "ontology_search",
+  "metadata",
+  "entity",
+  "state",
+  "history",
+  "why",
+  "transitions"
+]
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque lbb_inspect continuation. Repeat action and pass the returned next arguments; rejects changed metadata.",
+  "type": "string"
+}
    • addedInput schema / properties / page_size
      Added value: +{
+  "description": "Maximum complete metadata entries per page; defaults to 50. Nested fields are never truncated; an oversized single entry returns serialized_json fragments to concatenate and parse.",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / section
      Added value: +{
+  "description": "Optional top-level array to inspect, e.g. entity_type_defs, relation_defs, property_defs, classes, or relations. Omit to page through all sections.",
+  "type": "string"
+}
  7. Changed5 schema fields changedv0.4.2
    • changedInput schema / properties / action / description
      Previous value: -"Selects the variant (one of: guide, ontology, ontology_conformance, schema, ontology_search, metadata, entity, state, history, why, traverse, transitions)."New value: +"Selects the variant (one of: guide, ontology, ontology_conformance, schema, ontology_search, metadata, entity, state, history, why, transitions)."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "guide",
-  "ontology",
-  "ontology_conformance",
-  "schema",
-  "ontology_search",
-  "metadata",
-  "entity",
-  "state",
-  "history",
-  "why",
-  "traverse",
-  "transitions"
-]New value: +[
+  "guide",
+  "ontology",
+  "ontology_conformance",
+  "schema",
+  "ontology_search",
+  "metadata",
+  "entity",
+  "state",
+  "history",
+  "why",
+  "transitions"
+]
    • removedInput schema / properties / direction
      Removed value: -{
-  "enum": [
-    "out",
-    "in",
-    "both"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / max_hops
      Removed value: -{
-  "exclusiveMinimum": 0,
-  "maximum": 6,
-  "type": "integer"
-}
    • removedInput schema / properties / relations
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
  8. Changed12 schema fields changedv0.2.7
    • changedInput schema / properties / action / description
      Previous value: -"Selects the variant (one of: guide, ontology, ontology_conformance, schema, schema_audit, rules, schema_preview, ontology_search, metadata, entity, edges, state, history, why, traverse, transitions)."New value: +"Selects the variant (one of: guide, ontology, ontology_conformance, schema, ontology_search, metadata, entity, state, history, why, traverse, transitions)."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "guide",
-  "ontology",
-  "ontology_conformance",
-  "schema",
-  "schema_audit",
-  "rules",
-  "schema_preview",
-  "ontology_search",
-  "metadata",
-  "entity",
-  "edges",
-  "state",
-  "history",
-  "why",
-  "traverse",
-  "transitions"
-]New value: +[
+  "guide",
+  "ontology",
+  "ontology_conformance",
+  "schema",
+  "ontology_search",
+  "metadata",
+  "entity",
+  "state",
+  "history",
+  "why",
+  "traverse",
+  "transitions"
+]
    • removedInput schema / properties / base_ontology_version
      Removed value: -{
-  "minimum": 0,
-  "type": "integer"
-}
    • removedInput schema / properties / base_shapes_version
      Removed value: -{
-  "minimum": 0,
-  "type": "integer"
-}
    • removedInput schema / properties / cursor
      Removed value: -{
-  "description": "Opaque cursor from the previous page's `next_cursor`. The response is the unified list envelope { object:'list', data, has_more, next_cursor, total_count }; page a high-degree node (entity detail hard-caps its edge sample) by feeding next_cursor back here until has_more is false. Each row carries valid_time for a per-edge timeline.",
-  "type": "string"
-}
    • removedInput schema / properties / desired_mode
      Removed value: -{
-  "enum": [
-    "warn",
-    "reject"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / direction / description
      Removed value: -"Edges out of / into / touching the entity (default both)."
    • removedInput schema / properties / offset
      Removed value: -{
-  "description": "Legacy alias for `cursor` (still accepted); prefer paging with `cursor`.",
-  "minimum": 0,
-  "type": "integer"
-}
    • removedInput schema / properties / ontology
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "format": {
-      "enum": [
-        "auto",
-        "turtle",
-        "json_ld",
-        "rdf_xml",
-        "csv",
-        "tsv",
-        "lbb_json",
-        "spec"
-      ],
-      "type": "string"
-    },
-    "source": {
-      "description": "Ontology source text",
-      "type": "string"
-    }
-  },
-  "required": [
-    "source"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / relation / description
      Removed value: -"Filter to a single relation name."
    • removedInput schema / properties / row_limit
      Removed value: -{
-  "description": "Max edges returned this page (server caps at 1000; default 150).",
-  "exclusiveMinimum": 0,
-  "type": "integer"
-}
    • removedInput schema / properties / shapes
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "format": {
-      "enum": [
-        "auto",
-        "turtle",
-        "n_triples",
-        "n_quads",
-        "trig"
-      ],
-      "type": "string"
-    },
-    "source": {
-      "description": "SHACL/RDF shape source text",
-      "type": "string"
-    }
-  },
-  "required": [
-    "source"
-  ],
-  "type": "object"
-}
  9. First observedv0.2.1

TDQS

A4.2/5.0
Behavior5/5

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

The description goes well beyond the readOnlyHint annotation by disclosing important behavior: oversized records fail instead of truncating, page_size returns complete entries and may emit serialized_json fragments to concatenate, as_of_commit_seq pins retained history, schema-bound historical selection is unsupported, and omitting selectors preserves the native attributes/relationships view. These are exactly the behavioral traits an agent needs before calling the tool.

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?

The description is dense but front-loads the purpose and action list, then attaches high-value operational details to specific actions. Every sentence carries information and there is little redundancy. A bulleted action breakdown could improve scanability, but the content is appropriately sized for a 21-parameter multi-action tool.

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?

Given the lack of an output schema and the tool's complexity, the description supplies substantial return-value and failure-mode context for many actions, including ontology, schema, entity, publication, and ontology_conformance. It does not explain every action, such as guide or metadata, and some parameter interactions remain implicit, but it is largely complete for correct invocation.

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?

With 71% schema description coverage and 21 parameters, the schema already documents many inputs. The description adds meaningful semantics for key parameters such as page_size, section, cursor, as_of_commit_seq, entity_id, entity_type+key, and records/1 selectors. It does not clarify every parameter, such as detail, consistency, or status, but it substantially compensates for the remaining gaps.

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 opens with a specific verb and resource: "Read graph context and exact graph facts," then enumerates the available actions. It also distinguishes this tool from lbb_query for RDF/OWL axiom queries and SPARQL property paths. The multi-action nature makes it broader than a single-purpose tool, but the purpose is still clear.

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

Usage Guidelines4/5

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

It gives concrete routing guidance such as "graphs works before bootstrap," "schema reads active native ontology/SHACL metadata without running validation," and "Use lbb_query with SPARQL property paths for precise path selection." It also states that schema-bound historical selection is unsupported and that as_of should not be used for entity reads. It lacks a fully explicit when-not-to-use-this-tool rule, but the alternatives are clearly named.

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