Tessryx

Get resource graph

get_resource_graph

Read-onlyIdempotent

Browse how resources connect, in either direction. direction 'depends_on' (default) shows what this resource NEEDS, following 'depth' hops (default 3). direction 'depended_on_by' shows what would BREAK if you changed or deleted it — transitive and not depth-limited, since the chain (api template → the workflows calling it → the endpoints running those) is the answer; use it before a delete or a breaking edit. Each edge carries the reference text as authored, whether it names @published or @latest, and what that resolves to right now, so version drift is visible and not just connectivity. Check unscanned_kinds on a reverse result: a schema's referrers include every datafile and are too expensive to enumerate, so an empty answer there does NOT mean nothing depends on it. To find out whether something is broken rather than what it connects to, use analyze_resource.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes	the kind of resource to start from: workflow, dynamic_endpoint, api_template, datafile, schema, schedule, secret, custom_domain
`depth`	No	how many hops to follow (default 3). This is a browsing control for looking around; analyze_resource always follows chains to the end rather than stopping at a depth
`resource`	Yes	slug of the resource, optionally with a version suffix (e.g. 'blog/render' or 'blog/render@latest'); a bare slug means @published. For a custom_domain this is the hostname
`direction`	No	which way to walk: 'depends_on' (default — what this resource needs) or 'depended_on_by' (what would break if you changed or deleted it). depended_on_by is transitive: deleting an api template surfaces the workflows that call it AND the endpoints that run those workflows

Output Schema

TableJSON Schema

Name	Required	Description	Default
`root`	Yes
`edges`	Yes
`nodes`	Yes
`truncated`	No
`depth_exceeded`	No
`scan_truncated`	No
`unscanned_kinds`	No
`aggregate_referrers`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds valuable caveats about depended_on_by being transitive and the unscanned_kinds warning for reverse results, which go beyond the annotations.

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?

Each sentence adds value, but there is some redundancy: 'transitive and not depth-limited' is later repeated as 'depended_on_by is transitive', and 'version drift is visible' echoes 'what that resolves to right now'. Could be tightened without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the main use cases (pre-delete checks), explains transitive traversal, addresses the 'empty result does not mean no dependencies' caveat for unscanned kinds, and points to analyze_resource for breakage detection. This is complete for a graph traversal tool.

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

Parameters5/5

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

Schema already covers all parameters with descriptions, but the description adds meaningful context: depth is a browsing control, resource can have version suffixes, bare slug means @published, and custom_domain uses hostname. This goes beyond the schema's basic field descriptions.

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?

Clearly states it browses resource connections and distinguishes from analyze_resource by focusing on the graph structure rather than breakage detection. The verb 'browse' and object 'how resources connect' are specific and unambiguous.

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

Usage Guidelines5/5

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

Explicitly says to use it before delete or breaking changes, and provides the alternative analyze_resource for checking if something is broken. This leaves no ambiguity about when to choose this tool over siblings.

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

All Tessryx tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?