Skip to main content
Glama

HALOWERK EU Power Dispatch API

articles_id

GET fallback with a machine-readable 402 response for POST /articles/{id}.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorYes
endpointYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool returns a machine-readable 402 response, which is non-obvious behavior, but it does not explain what triggers the 402, whether authentication or payment is required, or whether the 402 is always returned.

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 a single compact sentence with no wasted wording, and the response behavior is front-loaded. Its terseness borders on cryptic, but it is appropriately sized for a zero-parameter endpoint.

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

Completeness3/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 402 response body. Still, for a tool whose only apparent purpose is to produce that 402 fallback, the description should clarify when to invoke it relative to articles_id_post; that usage context is missing.

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?

The tool has zero parameters and 100% schema description coverage, so there is no parameter meaning for the description to add. Baseline 4 applies.

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 identifies the resource (/articles/{id}), the HTTP method (GET), and the fallback role, and it implicitly distinguishes this from the POST sibling by referencing POST /articles/{id}. However, 'GET fallback' is jargon and the description never plainly states that the tool retrieves an article representation or always returns a 402, leaving the core purpose somewhat inferential.

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?

The description names POST /articles/{id} but does not say when an agent should call this GET fallback instead of articles_id_post, nor does it provide any when-not conditions. Usage is only implied by the word 'fallback'.

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