Skip to main content
Glama

Bildlinks der Freigabe-Karte erneuern

approval_page_urls_app
Read-only

Nur für die interaktive Freigabe-Karte: erneuert die zeitlich begrenzten Bildlinks der Briefseiten, wenn die alten abgelaufen sind. EN: For the interactive approval card only: renews the time-limited image links of the letter pages once the old ones have expired.

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": {
      "approvalId": "<approvalId>"
    },
    "name": "approval_page_urls_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
approvalIdYes

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful context that the links are time-limited and espace on expiry, but says nothing about whether renewal invalidates previously issued links, what auth/ownership is required on the approval, or what the caller receives back.

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?

Front-loaded with the crucial restriction, which is good, but the German and English sentences are verbatim duplicates, doubling length without adding new information. Two sentences would suffice instead of four.

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?

For a trivial single-parameter read tool the purpose is adequately conveyed, but with no output schema the description should state that fresh URLs are returned (and whether the old ones stop working) — an agent cannot otherwise predict the response payload.

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 0% and the sole parameter approvalId (uuid) is never mentioned or elaborated in the description. The name is self-explanatory enough that an agent will infer it is the approval whose card links need refreshing, but the description does not compensate for the coverage gap by stating format, source, or validation.

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?

Names a specific verb (renews) and resource (time-limited image links of letter pages), and scopes it to the interactive approval card, which separates it from letter_page_urls_app and template_page_urls_app. It does not name those siblings explicitly, but the scope qualifier does the distinguishing work.

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

Usage Guidelines4/5

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

Gives a clear trigger condition ('once the old ones have expired') and an explicit applicability restriction ('only for the interactive approval card'), which effectively excludes the non-app contexts. It stops short of naming the alternative tools to use for letters/templates.

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.