Skip to main content
Glama

HALOWERK EU Power Dispatch API

research_quick

Research and market-monitoring agents buy this endpoint to answer a focused question with a compact live market snapshot.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
sourcesNo

Output Schema

NameRequiredDescriptionDefault
queryYes
sourceYes
timestampYes
current_priceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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 disclosure burden. It does add two behavioral signals — 'live' (data freshness) and 'compact' (small response) — but says nothing about auth, rate limits, cost, or what happens with an empty 'sources' list, which matters for a 2-parameter tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence keeps it short and the functional part is front-loadable, but roughly half the sentence is marketing framing ('agents buy this endpoint') that adds no operational value for an agent deciding how to call the tool.

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 explained, but the definition still omits how to use 'sources', how this differs from the plain 'research' sibling, and any behavioral caveats. For a tool with no annotations and undocumented parameters, this leaves too much to inference.

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%, so the description must compensate. It vaguely suggests the 'query' should be focused, but never names the 'query' or 'sources' parameters, explains what 'sources' accepts, or whether omitting it changes the search scope. Most parameter meaning is left undefined.

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

Purpose3/5

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

The sentence conveys the resource loosely ('a focused question', 'compact live market snapshot') and implies a lightweight research lookup, but never uses a specific verb such as 'query' or 'search', and it does not distinguish this tool from the sibling 'research' or 'research_post'. An agent can guess the general function but not its precise scope.

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?

'To answer a focused question' hints at narrow lookups, but there is no explicit when-to-use, when-not-to-use, or named alternative despite siblings like 'research' existing. The opening clause about agents 'buying this endpoint' is positioning copy, not selection guidance.

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