Skip to main content
Glama
littlebigbrains

@littlebigbrain/mcp

by littlebigbrains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

lbb_inspect

Read-only

Inspect a Little Big Brain graph's ontology, schema, metadata, entities, and publication state. Verify graph facts and pending ontology suggestions before querying or writing.

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). 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 returns one node's attributes and current relationships from the RDF read. For a node's past values, run SPARQL with as_of_commit_seq through lbb_query. Use lbb_query with SPARQL property paths for precise path selection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
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.
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.
entity_typeNo
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. 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."
  2. 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"
+}
  3. 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"
-}
  4. Changed1 schema field changedv0.5.2
    • removedInput schema / properties / branch
      Removed value: -{
-  "description": "Branch to target; defaults to the connection's branch",
-  "type": "string"
-}
  5. 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"
+}
  6. 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"
-}
  7. 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"
-}
  8. First observedv0.2.1

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint=true already covering the safety profile, the description still adds real behavioral context: pagination contract ('follow next until absent'), cursor semantics ('rejects changed metadata'), oversized-entry fragmentation into serialized_json, that 'publication reports whether writes are queryable', and that ontology_conformance serves a durable report pinned to the published root. It does not describe permissions, rate limits, or failure modes.

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

Conciseness3/5

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

The content is proportionate to a 10-action, 15-parameter dispatcher, and the action inventory is front-loaded. However it is delivered as one dense unstructured block with no bullets or line breaks, and the action list partly duplicates the schema's action enum description, so it is harder to scan than it needs to be.

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?

There is no output schema and no nested objects, so the description carries the return-shape burden and does so for most actions (pagination, fragment reassembly, entity output, publication flag). It omits what guide, metadata, and ontology_search return, and never explains the query/top_k search parameters, leaving a few gaps for a tool this broad.

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 73% and the action enum is already self-documenting in the schema, but the description adds substantial semantic meaning: it explains what each action returns (ontology/schema give complete entries with page_size/section/cursor; entity returns attributes and current relationships) and reinforces that as_of is unsupported for entity. It leaves limit, detail, top_k and metadata unaddressed in prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource ('Read graph context and exact graph facts') and then enumerates the ten specific inspection resources (guide, graphs, publication, ontology, schema, entity, etc.). It explicitly distinguishes itself from the sibling lbb_query twice ('Query asserted RDF/OWL axioms separately with lbb_query', 'Use lbb_query with SPARQL property paths'), so an agent can route correctly without opening either schema.

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?

Gives per-action usage context (e.g., 'graphs works before bootstrap', 'ontology_suggestions lists the ontology change suggestions that wait for review', 'For a node's past values, run SPARQL with as_of_commit_seq through lbb_query'). It clearly names alternatives for the read-vs-query decision, though it never contrasts itself with other read siblings like lbb_rdf or lbb_models, and the other nine sibling tools go unmentioned.

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