Skip to main content
Glama

raumnebenan

Get article details by UUIDs

get_article_details_by_uuids
Read-onlyIdempotent

Fetches complete article details (full markdown body content, author, publishing dates, tags, and related article links) for an array of article UUID strings. Prefer get_article_details_by_slugs when slugs are known; use this tool when you already have article UUIDs (e.g. from list_articles or previous lookups).

Input Schema

NameRequiredDescriptionDefault
article_uuidsYesAn array of 1–10 article UUIDs to fetch details for.

Output Schema

NameRequiredDescriptionDefault
dataYes
sourceYes
retrieved_atYes
copyright_holderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / data / properties / next_page
      Added value: +{
      +  "description": "The next page number; absent on the last page.",
      +  "minimum": 2,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / data / properties / page
      Added value: +{
      +  "description": "The returned page (1-based).",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / data / properties / per
      Added value: +{
      +  "description": "Items per page.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. Changed5 schema fields changed
    • addedInput schema / properties / article_uuids / items / format
      Added value: +"uuid"
    • addedInput schema / properties / article_uuids / items / minLength
      Added value: +1
    • addedInput schema / properties / article_uuids / minItems
      Added value: +1
    • addedInput schema / properties / article_uuids / uniqueItems
      Added value: +true
    • changedOutput schema / properties / data / properties / hint / description
      Previous value: -"Guidance for the agent when no articles were found."New value: +"Guidance for the agent when no articles were found or some requested identifiers could not be resolved."
  3. Changed9 schema fields changed
    • addedInput schema / properties / article_uuids / description
      Added value: +"An array of 1–10 article UUIDs to fetch details for."
    • addedInput schema / properties / article_uuids / items / maxLength
      Added value: +36
    • addedInput schema / properties / article_uuids / maxItems
      Added value: +10
    • removedOutput schema / properties / articles
      Removed value: -{
      -  "items": {
      -    "properties": {
      -      "article_slug": {
      -        "type": "string"
      -      },
      -      "article_uuid": {
      -        "type": "string"
      -      },
      -      "author": {
      -        "type": "string"
      -      },
      -      "body_markdown": {
      -        "type": "string"
      -      },
      -      "category": {
      -        "type": "string"
      -      },
      -      "copyright_holder": {
      -        "type": "string"
      -      },
      -      "is_part_of_story": {
      -        "type": "string"
      -      },
      -      "last_article_update": {
      -        "type": "string"
      -      },
      -      "original_publishing_date": {
      -        "type": "string"
      -      },
      -      "related_articles_by_friendly_url": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "source_url": {
      -        "type": "string"
      -      },
      -      "summary": {
      -        "type": "string"
      -      },
      -      "tags": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "title": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [],
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • addedOutput schema / properties / copyright_holder
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / data
      Added value: +{
      +  "properties": {
      +    "articles": {
      +      "description": "The list of articles.",
      +      "items": {
      +        "properties": {
      +          "article_slug": {
      +            "type": "string"
      +          },
      +          "article_uuid": {
      +            "format": "uuid",
      +            "type": "string"
      +          },
      +          "author": {
      +            "type": "string"
      +          },
      +          "body_markdown": {
      +            "type": "string"
      +          },
      +          "category": {
      +            "type": "string"
      +          },
      +          "copyright_holder": {
      +            "type": "string"
      +          },
      +          "is_part_of_story": {
      +            "type": "string"
      +          },
      +          "last_article_update": {
      +            "format": "date-time",
      +            "type": "string"
      +          },
      +          "original_publishing_date": {
      +            "format": "date-time",
      +            "type": "string"
      +          },
      +          "related_articles_by_friendly_url": {
      +            "description": "Slugs of related articles.",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "source_url": {
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "summary": {
      +            "type": "string"
      +          },
      +          "tags": {
      +            "description": "Tags for the article.",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "title": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "source_url",
      +          "copyright_holder",
      +          "original_publishing_date",
      +          "last_article_update",
      +          "title",
      +          "summary",
      +          "article_slug",
      +          "related_articles_by_friendly_url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "hint": {
      +      "description": "Guidance for the agent when no articles were found.",
      +      "type": "string"
      +    },
      +    "invalid": {
      +      "description": "List of requested identifiers that were invalid.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "not_found": {
      +      "description": "List of requested identifiers that were not found.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "description": "The total number of articles.",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "unavailable": {
      +      "description": "List of requested identifiers that could not be fetched due to upstream issues.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "articles"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / retrieved_at
      Added value: +{
      +  "format": "date-time",
      +  "type": "string"
      +}
    • addedOutput schema / properties / source
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[]New value: +[
      +  "source",
      +  "copyright_holder",
      +  "retrieved_at",
      +  "data"
      +]
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral value by specifying the returned payload contents (full markdown body, related links), which goes beyond 'details', though it says nothing about batching cost or why the 1–10 cap exists.

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

Conciseness5/5

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

Two sentences, zero filler, with the core purpose first and the sibling-routing rule second. Every clause earns its place.

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

Completeness5/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 needn't be explained, and the input is a single fully-documented parameter. The description still names the key payload fields and the disambiguation rule, leaving nothing an agent needs in order to call it correctly.

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 array parameter already documents its UUID items, min/max items, and uniqueness. The description only restates 'array of article UUID strings', adding no format or edge-case guidance beyond the schema — baseline 3.

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

Purpose5/5

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

States a specific verb (fetches) and resource (complete article details) and enumerates the payload (markdown body, author, publishing dates, tags, related links). It also names the sibling it is not — get_article_details_by_slugs — so an agent can discriminate without opening the schema.

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

Usage Guidelines5/5

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

Explicit routing rule: prefer the slug variant when slugs are known, use this one when UUIDs are already in hand, with concrete sources ('e.g. from list_articles or previous lookups'). Both the when and the alternative are stated.

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