Skip to main content
Glama
Sign In

Warmth Engine Observatory

by com.warmthengine
OverviewDiscussionsAdmin

Get Sovereign Capability Profile Actors

get_actors
Read-onlyIdempotent

Retrieve whole Sovereign Capability Profile (SCP) actors — each with its designation (PAA / AIK / ACS / Participant), capability score, severance result, assessed (the register month, YYYY-MM, the profile was assessed in), a met/not-met assessment across the seven capability dimensions (D1–D7), and energy_context. Use to fetch complete actor records; to pivot one dimension across all actors, compare actors side by side, or read the dimension-watch register, use query_scp. Filter by designation or actor name. Free tier returns each dimension's met status and recorded headline (and the US sample in full); full tier adds the per-dimension constraint, qualification, and sources. energy_context carries installed generation capacity from the U.S. Energy Information Administration and annual electricity generation from the energy think tank Ember, served in full on both tiers: external reference data outside the WEO analytical stack, national totals, dated observations reported as published, accompanying the profiles but forming no part of them. Descriptive — recorded status, never inference.

Input Schema

NameRequiredDescriptionDefault
actor_nameNoFilter by actor code (ISO 3166-1 alpha-2, exact, e.g. "CN") or name (partial match, e.g. "China"). Named `actor` in `get_capability_links`.
designationNoFilter by designation: PAA, AIK, ACS, Participant

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / designation / enum
      Added value: +[
+  "PAA",
+  "AIK",
+  "ACS",
+  "Participant"
+]
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changed
    • changedInput schema / properties / actor_name / description
      Previous value: -"Filter by actor code (exact, e.g. \"CN\") or name (partial match, e.g. \"China\"). Named `actor` in `get_capability_links`."New value: +"Filter by actor code (ISO 3166-1 alpha-2, exact, e.g. \"CN\") or name (partial match, e.g. \"China\"). Named `actor` in `get_capability_links`."
  4. Changed1 schema field changed
    • changedInput schema / properties / actor_name / description
      Previous value: -"Filter by actor name (partial match)"New value: +"Filter by actor code (exact, e.g. \"CN\") or name (partial match, e.g. \"China\"). Named `actor` in `get_capability_links`."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: tier-dependent content (free tier returns met status and headline per dimension; full tier adds constraint, qualification, and sources), the provenance and tier-independence of energy_context, and the crucial 'Descriptive — recorded status, never inference' framing. This is behavior an agent could not infer from the annotations.

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?

Front-loaded with the retrieval action and its payload, then routing, then tier behavior — a sensible order. However, the energy_context clause is wordy and restates the same idea several times ('external reference data outside the WEO analytical stack, national totals, dated observations reported as published, accompanying the profiles but forming no part of them'), which could be tightened without losing meaning.

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?

With no output schema, the description carries the burden of explaining returns and does so thoroughly: the field set, the free-vs-full tier split, and what energy_context does and does not contain. Combined with the sibling routing for query_scp, an agent has everything needed to call it correctly.

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 both parameters (actor_name, designation) are already fully documented in the schema, including the ISO code vs partial-name matching and the cross-tool naming note. The description's 'Filter by designation or actor name' adds no syntax or semantics beyond the schema, so the baseline 3 applies.

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 gives a specific verb ('Retrieve') and resource ('whole Sovereign Capability Profile (SCP) actors'), then enumerates the exact fields returned (designation, capability score, severance result, assessed, D1–D7 met/not-met, energy_context). It explicitly names the sibling it is not — 'to pivot one dimension across all actors ... use query_scp' — so an agent can discriminate without opening either schema.

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 primary use ('fetch complete actor records') and names three concrete alternative scenarios (pivot one dimension, compare actors side by side, read the dimension-watch register) that route to query_scp instead, plus the filter options. When-to-use, when-to-use-something-else, and the selecting condition are all explicit.

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