Skip to main content
Glama

Warmth Engine Observatory

by com.warmthengine

get_capability_links

Retrieve the event↔dimension membership links — which events qualify or contribute to each actor's Sovereign Capability Profile (SCP) capability dimensions. Filter by actor (e.g. "US", "CN", "GB" — note GB, not UK), dimension (D1–D7), or event_id. Each link carries its link_type (qualifying_contributor = establishes the dimension vs capability_area = contributes to it), attribution (specific | general), and entity (the named asset, on qualifying links only); its identity and lifecycle — link_id (the stable handle, CL-{ACTOR}-{Dn}-{eventID}.{sequence}), created, scp_register_version (the register cycle it was assessed in), assessed_under (the methodology version in force at that assessment, which may be older than the dataset's current one), status, and on retired links status_changed; and at full tier qualification_basis, rationale and note (the deep qualification analysis), status_reason (the assessed reasoning for a retirement), and provenance (construction-cohort marker). Sole-vs-multiple basis is derivable by counting qualifying_contributor links per actor×dimension (1 = sole; >1 = one of several) — links are never flattened to qualifies:yes/no. Active links are returned by default; retired links are never restored, and a relationship assessed afresh enters as a new link at the next sequence. Pass include_retired to receive the archive alongside the active links. The response carries a metadata block — totals by type, per-actor and per-dimension distributions, active/retired status_counts, met-dimension coverage figures, and the dataset's generation date and revision history — identical on both tiers; last_updated dates the most recent revision. For the higher-order signatures built from these links, use get_capability_signatures.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorNoActor code filter (ISO 3166-1 alpha-2; EU for the European Union): US, CN, EU, FR, GB, IN, JP, KR, NL, SA, TW. Named `actor_name` in `get_actors`.
event_idNoEvent id filter, e.g. "196"
dimensionNoDimension code filter: D1–D7
include_retiredNoInclude retired links alongside active ones (default false — active only). Retired links are frozen snapshots of links that no longer qualify; use this to reconstruct a past state, not to read current membership.

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full disclosure burden and does so thoroughly. It explains active-by-default behavior, that retired links are never restored, that fresh assessments create new links rather than mutating old ones, and details the lifecycle fields including status_changed. It also clarifies that sole-vs-multiple basis must be derived by counting rather than assumed from a flattened flag.

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?

The description is long, but every section earns its place given the tool's complexity and the absence of an output schema. It is front-loaded with purpose and filtering, then moves through link fields, lifecycle, defaults, metadata, and finally the sibling pointer. It could be tightened, but the structure is logical and dense with necessary 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?

For a complex tool with no output schema and no annotations, the description leaves almost nothing ambiguous: it covers link semantics, field meanings, lifecycle behavior, default and archive modes, metadata contents, and the alternative tool. The only minor omitted detail is whether multiple filters combine with AND or OR, but this is not enough to reduce completeness given the overall richness.

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, but the description adds genuine value beyond the schema: it gives concrete actor examples with the important GB-not-UK warning, defines link_type and attribution semantics, and reframes include_retired as a way to reconstruct past state rather than a simple boolean toggle. The description does not over-explain what the schema already documents, but it adds enough to justify a 4.

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 opening sentence states a specific verb and resource: 'Retrieve the event↔dimension membership links' for SCP capability dimensions. It clearly distinguishes itself from the sibling tool by ending with 'For the higher-order signatures built from these links, use get_capability_signatures.' An agent can immediately identify what this tool returns and how it differs from the most similar alternative.

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?

The description explicitly says to filter by actor, dimension, or event_id and explains when to pass include_retired: 'use this to reconstruct a past state, not to read current membership.' It also names the alternative tool for higher-order signatures, so an agent knows when not to use this one. This is strong, actionable routing guidance.

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

All Warmth Engine Observatory toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool targets a distinct data slice or operation. For example, `get_actors` retrieves full actor profiles while `query_scp` offers pivoting and comparison; `search_events` finds event IDs and `get_event` retrieves a full record; `get_threads` provides material links separate from `traverse_coordination` for lineage walks. There is no overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent `verb_noun` pattern with underscore separators. Most use `get_` for retrieval, with `query_scp`, `search_events`, and `traverse_coordination` using different verbs that accurately reflect their distinct actions. The naming is predictable and intuitive.

Tool Count5/5

16 tools is well-scoped for the complexity of an observation platform that covers actors, blocs, events, connections, topology, vocabulary, statistics, and material links. Each tool earns its place by covering a necessary query pattern without unnecessary fragmentation.

Completeness5/5

The tool set provides comprehensive coverage of the domain: actor retrieval and querying (profiles, comparisons, watch), bloc membership, event discovery and full records, connection traversal and filtering, structural topology, material links, vocabulary lookups, and summary statistics. No obvious gaps in read access are present.

Resources