Skip to main content
Glama

describe_kg_schema

Read-only

Describes an Otto/Now Assist Knowledge Graph schema by listing nodes (tables, labels, properties) and edges (relationships) from graph records or fallback schema JSON.

Instructions

Describe one Knowledge Graph schema (sys_meta_graph) used by Otto / Now Assist: its nodes (tables, labels, properties) and edges (relationships). Reads sys_meta_graph_node / sys_meta_graph_edge, falling back to the graph schema_json.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "graph": "<graph>"
    },
    "name": "describe_kg_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
graphYesGraph sys_id or name, e.g. now_user_graph, hrsd_knowledge_graph
include_propertiesNoInclude node property lists (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful context beyond that: it discloses the backing sources (sys_meta_graph_node / sys_meta_graph_edge) and a fallback path to schema_json, which tells an agent what happens when the primary tables lack data.

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?

Two tight sentences with zero filler; the core purpose and returned content are front-loaded before the implementation detail about source tables and fallback.

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 two-parameter read-only tool with full schema coverage and no output schema, the description supplies enough: what is described, what is returned, and where the data comes from. Only a note on output shape or scale (e.g., large graphs) would add value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters (graph, include_properties) are already documented in the schema, including the default of true and sys_id-or-name examples. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 uses a specific verb ('Describe') plus a precise resource ('one Knowledge Graph schema (sys_meta_graph)') and enumerates the returned content: nodes (tables, labels, properties) and edges (relationships). It clearly differs from a generic table-schema tool, but it never names or contrasts a sibling such as get_table_schema, so it stops short of full sibling differentiation.

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 only implied by the phrase 'used by Otto / Now Assist', which hints at the KG context where this applies. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for adjacent schema needs.

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