Skip to main content
Glama

HALOWERK EU Power Dispatch API

research_post

Returns aggregated energy research for Germany and the EU from live data sources.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "research_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
sourcesNo

Output Schema

NameRequiredDescriptionDefault
successYes
summaryYes
key_metricsYes
confidence_scoreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only says results are 'aggregated' from 'live data sources'. It does not disclose latency or cost (research calls are typically slow), whether the call is synchronous or job-creating despite the '_post' suffix, rate limits, or auth requirements.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity comes at the cost of the missing guidance noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, but for a two-parameter tool with zero schema coverage and no annotations the definition is under-specified. Nothing tells the agent how to form the required 'query' or what 'sources' accepts.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description must compensate and largely fails: 'query' is never explained (free text? topic? region?) and 'sources' is only faintly gestured at by 'live data sources', with no indication of allowed values or defaults. The agent is left guessing at the shape of the required input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns aggregated energy research') plus scope ('Germany and the EU') and data provenance ('live data sources'). It does not distinguish itself from the sibling tools 'research' and 'research_quick', so an agent cannot tell from the text alone which of the three to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of the obvious alternatives ('research', 'research_quick') despite their presence as siblings. The agent must infer the choice entirely from the name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources