Football Atlas

Traverse the Football Atlas knowledge graph

get_related

Read-onlyIdempotent

Graph neighbours of an object: outgoing and incoming relations, each with its relation type. PAGED: 25 relations by default, 200 at most, and a response budget of about 64 KB per call — a page over budget comes back shorter WITH a next_cursor, never truncated. One cursor walks both directions, outgoing first; its absence means you have the last page. Use this after get_entity to widen an answer with adjacent objects. It walks one hop from an id you already have — use search when you have a question and no starting object.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The knowledge object to walk out from, by id.
`limit`	No	How many relations to return, across both directions. Defaults to 25.
`cursor`	No	Continue from a previous call: pass the next_cursor it returned. Opaque; do not construct one.

Output Schema

TableJSON Schema

Name	Required	Description
`found`	Yes
`total`	No	How many relations this object has in both directions, before paging.
`incoming`	No
`outgoing`	No
`recovery`	No
`returned`	No
`next_cursor`	No	Pass to the next call to continue. ABSENT means this was the last page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 7, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Continue from a previous call: pass the next_cursor it returned. Opaque; do not construct one.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "How many relations to return, across both directions. Defaults to 25.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / next_cursor

Added value: +{
+  "description": "Pass to the next call to continue. ABSENT means this was the last page.",
+  "type": "string"
+}

addedOutput schema / properties / returned

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / total

Added value: +{
+  "description": "How many relations this object has in both directions, before paging.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changed2 schema fields changedSep 6, 2026

addedOutput schema / properties / incoming / items / properties / entity / properties / x

Added value: +{
+  "additionalProperties": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "description": "Indexed instance-specific attributes, grouped by namespace — the same fields api/index.json publishes. Absent when the instance declares none.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / outgoing / items / properties / entity / properties / x

Added value: +{
+  "additionalProperties": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "description": "Indexed instance-specific attributes, grouped by namespace — the same fields api/index.json publishes. Absent when the instance declares none.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 1, 2026
- addedInput schema / properties / id / description
```
Added value: +"The knowledge object to walk out from, by id."
```

Changed1 schema field changedAug 26, 2026

addedOutput schema / properties / recovery

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "available": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "available_count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "available_truncated": {
+      "type": "boolean"
+    },
+    "did_you_mean": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "hint": {
+      "type": "string"
+    },
+    "next_tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "available_count",
+    "available",
+    "next_tool",
+    "hint"
+  ],
+  "type": "object"
+}

First observedAug 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description goes well beyond the annotations by detailing pagination behavior: default and maximum limits, a 64 KB response budget, short pages with next_cursor rather than truncation, cursor direction order, and how to detect the last page. This is rich behavioral disclosure.

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 dense but well-structured: definition first, then pagination mechanics, then usage guidance with sibling alternatives. Every sentence carries useful information and none are redundant with the schema or annotations.

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?

The tool is fully specified for an agent to call correctly: the starting id requirement, pagination rules, cursor semantics, ordering, and when to choose this tool over alternatives are all covered. The output schema handles return value documentation, so the description does not need to repeat it.

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 100%, so the baseline is 3. The description adds extra semantic value beyond the schema by explaining that the cursor is opaque, one cursor walks both directions with outgoing first, and page size interacts with the response budget. This justifies a score above baseline.

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?

The description states a specific action and resource: graph neighbours of an object with outgoing and incoming relations and relation types. It also distinguishes itself from siblings by explicitly positioning itself after get_entity and contrasting with search.

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?

It gives explicit usage context: use after get_entity to widen an answer, and use search when you have a question and no starting object. This clearly routes the agent to the correct tool among siblings.

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

All Football Atlas 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.