Skip to main content
Glama

HALOWERK EU Power Dispatch API

articles_id_post

Returns the full text of one energy trade article; article ids and titles come from the free GET /articles catalog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "articles_id_post"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
typeYes
articleYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does convey a read-style retrieval and the catalog dependency, which is useful context. The word "free" applied to the catalog hints that this endpoint may be metered or paid, but that is never stated, and there is no mention of auth requirements, rate limits, or truncation of long articles.

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, and the catalog dependency is attached efficiently via a semicolon. It is slightly under-specified for the ambiguity it leaves about article selection, but nothing is wasted.

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?

An output schema exists, so the description need not explain the returned article body, and for a zero-parameter read tool the remaining burden is small. The one unresolved item is how the article is identified given the id-bearing tool name and an empty parameter object.

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?

The schema declares zero properties, so the baseline would be 4, but the description actively raises a question it does not answer: it says ids come from the catalog, yet there is no parameter through which to pass an id. The reader is left unsure how the target article is selected, which is a semantic gap the description creates rather than resolves.

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?

The description names a specific verb and resource ("Returns the full text of one energy trade article") and distinguishes itself from the catalog endpoint by pointing at "the free GET /articles catalog" as the source of ids and titles. It is clear what the tool produces, though it never reconciles the "one article" framing with the fact that the tool takes no identifier.

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?

It implies a workflow (fetch ids/titles from the catalog first, then call this to get full text), which is real usage guidance. It gives no explicit when-not condition, no statement about what happens on an invalid or unknown article, and no alternative for retrieving summaries versus full text.

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