Skip to main content
Glama
Sign In

Warmth Engine Observatory

by com.warmthengine
OverviewDiscussionsAdmin

Get Coordination Connections

get_connections
Read-onlyIdempotent

Retrieve Coordination Connections (CCs) — the typed, directional relationships WEO records between events — optionally filtered by event (as source or target), type (1–7), or confidence (CC-V / CC-E / CC-A). For a single CC by its identifier, use get_connection_by_id. Each CC carries its id, source/target event IDs, type name + number, confidence, and direction; full tier — and either tier when an endpoint is a sample event — adds the evidence summary, evidence detail, and verification history.

Input Schema

NameRequiredDescriptionDefault
event_idNoReturn only CCs involving this event (as source or target)
confidenceNoFilter by confidence level: CC-V, CC-E, CC-A
connection_typeNoFilter by CC type (1–7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / confidence / enum
      Added value: +[
+  "CC-V",
+  "CC-E",
+  "CC-A"
+]
    • addedInput schema / properties / connection_type / enum
      Added value: +[
+  1,
+  2,
+  3,
+  4,
+  5,
+  6,
+  7
+]
    • removedInput schema / properties / connection_type / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / connection_type / minimum
      Removed value: --9007199254740991
    • changedInput schema / properties / connection_type / type
      Previous value: -"integer"New value: +"number"
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context by explaining the returned fields and the tier-dependent inclusion of evidence summaries, evidence detail, and verification history, though it does not cover pagination or ordering behavior.

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 definition is front-loaded and dense with useful information, with no redundant background. It is slightly long and compound in places, but every sentence contributes either selection guidance or return-value context.

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?

There is no output schema, so the description carries the return-value burden, and it does explain the core CC fields plus tier-dependent evidence fields. It does not mention pagination, result limits, or ordering, which keeps it from being fully complete.

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 100%, and the description largely restates the filters already documented in the schema: event as source/target, type 1–7, and confidence values. The baseline of 3 is appropriate because the schema carries the parameter semantics.

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 uses a specific verb and resource ('Retrieve Coordination Connections') and explains what CCs are as typed directional relationships between events. It explicitly distinguishes the single-record sibling `get_connection_by_id`, so an agent can select this tool without opening schemas.

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 states the optional filter dimensions (event as source or target, type, confidence) and explicitly routes single-CC lookups to `get_connection_by_id`. This gives clear when-to-use and when-to-use-the-alternative 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
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources