Skip to main content
Glama

Stand einer Veröffentlichung

publish_status
Read-only

Wie weit ist eine laufende Veröffentlichung? Kennung aus publish.

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": {
      "run": "<run>"
    },
    "name": "publish_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
runYesKennung aus publish

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful qualifier that the tool concerns a *running* (in-flight) publication, but it says nothing about what happens for unknown or already-finished IDs, nor about polling behavior.

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?

Two very short sentences, front-loaded with the question the tool answers, with no filler. The interrogative phrasing is slightly informal but efficient and easy to parse.

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?

There is no output schema, so the agent must infer what a status response looks like; the description gives no hint about progress fields or possible completion/failure states. For a simple single-parameter status lookup this is tolerable, but it leaves the return side undefined.

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 the single parameter's schema text is identical to the description's phrase 'Kennung aus publish', so the description adds no meaning beyond the schema. Baseline 3 applies since the schema carries this burden fully.

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 states a specific resource and intent: querying how far along ('Wie weit ist') a running publication is. The reference to 'Kennung aus publish' implicitly distinguishes it from the sibling publish tool, which starts a run rather than reporting on one.

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?

The phrase 'Kennung aus publish' signals the prerequisite and the typical sequence (start with publish, then poll this), so usage is implied. However, there is no explicit statement of when to use it versus alternatives, nor any guidance on repeated polling, timing, or when a run is considered finished.

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