Al Jazeera 360

build_knowledge_graph

Read-only

Build a knowledge graph of entities (topics, countries, people) from content titles.

Extracts named entities from video titles across sections and builds
a network showing how topics, countries, and themes interconnect.

Args:
    sections: Comma-separated section IDs (default: AJA,AJD)

Returns:
    JSON with entity network, top entities, co-occurrence matrix, and insights

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sections`	No		AJA,AJD

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the tool is known to be safe and non-mutating. The description adds the return format but doesn't disclose potential costs, time, or limitations of analysis. With annotation coverage, this is a reasonable but not outstanding score.

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 neatly structured with a purpose statement, Args, and Returns sections. It is concise, front-loaded, and contains no filler or redundancy.

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?

Given a single optional parameter with a default and an output schema present, the description covers the key inputs and returns adequately. Missing explicit when-to-use guidance is a minor gap but not critical for a simple read-only tool.

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 description coverage is 0%, and the schema only shows type and default. The description's Args section compensates by explaining that sections are comma-separated section IDs with default 'AJA,AJD', adding meaning beyond the schema.

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 opens with a specific verb and resource: 'Build a knowledge graph of entities (topics, countries, people) from content titles.' It clearly states the extraction process and output, distinguishing it from siblings like build_topic_clusters by focusing on entity network and co-occurrence.

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?

The description provides context about operating across sections and defaults for sections, but it never states when to choose this tool over alternatives like build_topic_clusters or compare_sections, nor any exclusions. The usage context is implied rather than explicit.

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

All Al Jazeera 360 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.