Machine Schema

Traverse the graph

get_related

Read-onlyIdempotent

List entries connected to an id, in both directions: a robot's manufacturer, controllers and protocols, a controller's robots and alarm codes, or a base model's variants.

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": {
      "id": "<id>"
    },
    "name": "get_related"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`edge`	No	Limit to one relationship type
`limit`	No

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful traversal behavior beyond that: results are listed 'in both directions' and span several concrete relationship types. It does not cover pagination or limit defaults, but the key traversal semantics are disclosed.

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?

The description is a single, front-loaded sentence with no wasted language. It presents the core action, scope, and illustrative relationship types efficiently.

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

Completeness3/5

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

With annotations covering safety and an output schema available, the description is sufficient for basic invocation. However, it omits limit behavior and explicit sibling routing, leaving some gaps for an agent choosing and configuring the call.

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 only 33%, so the description must compensate. It clarifies that 'id' is the starting entry and provides examples corresponding to relationship types, but it does not explain the 'limit' parameter or the format/semantics of 'id'. This is adequate but incomplete.

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 states a specific verb and resource: 'List entries connected to an id' with 'both directions' scope. It also gives concrete relationship examples, making the graph-traversal purpose clear, though it does not explicitly distinguish itself from siblings like get_entry or search_entries.

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 implied by the relationship examples (manufacturer, controllers, protocols, variants), indicating when graph traversal is appropriate. However, there is no explicit guidance on when to use this versus get_entry, search_entries, or other siblings.

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

All Machine Schema 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?