Skip to main content
Glama

Engagement Graph Schema + Examples (for traverse_graph)

traverse_graph_help
Read-onlyIdempotent

[Meta · free] Returns the schema, FK edges, and 5 canonical SQL examples needed to write your own SELECT against the engagement graph via traverse_graph. Also returns YOUR resolvable identities (caller_user_ids, caller_tracked_lp_ids) — substitute these into example SQL when you write your query. Pure DB read — 0 credits. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description's real addition is the cost signal ('0 credits', 'free') and the fact that the response is personalized with the caller's own resolvable identities — useful context the annotations do not carry, though nothing is said about response size or how the examples are structured.

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?

Front-loaded with the '[Meta · free]' tag and a single dense sentence covering return contents and the identity substitution instruction. Slightly redundant at the tail ('Pure DB read — 0 credits. Free.') where the free/cost point is stated three times across the entry.

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 no output schema, the description must enumerate what comes back, and it does: schema, FK edges, five canonical examples, and caller identities. It is complete enough to invoke correctly; only the exact shape of the returned examples (e.g., whether they are keyed or plain SQL blocks) is left implicit.

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 applies. The description correctly does not invent parameter semantics, instead directing attention to the identity values that appear in the returned payload.

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 and payload: returns the schema, FK edges, and 5 canonical SQL examples for writing SELECTs against the engagement graph via traverse_graph. It also distinguishes itself from the sibling traverse_graph by being the meta/authoring aid rather than the execution tool, and names the secondary return value (caller_user_ids, caller_tracked_lp_ids).

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?

The usage context is clear: call this to obtain the schema and examples you need before writing your own query through traverse_graph, and substitute your own resolvable identities into the example SQL. There are no explicit exclusions or redirects (e.g., 'use the canned tools instead of raw SQL if...'), so it stops short of a full 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources