Skip to main content
Glama

Generate artwork credits and citations

still_generate_citation
Read-onlyIdempotent

Format website/social credits, figure captions, Chicago 18, MLA 9 or APA 7 using the same engine as the STILL website. Supply exactly one of record or supported sourceUrl. One academic style per call. Preserve warnings and separate sourceRecommendedCitation. No image-use permission is granted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoRequired for academic outputs: Chicago 18, MLA 9, APA 7. One style per call.
localeNoFormatting locale; does not translate source metadata.en
recordNoSupplied metadata; use exactly one of record or sourceUrl.
targetNoartwork
outputsYesCredit outputs: website_credit, social_credit, figure_caption. Academic: bibliography, full_note (Chicago only), in_text (MLA/APA only).
sourceUrlNoFetch an artwork record from The Met or Cleveland. Use record for other sources or museum_page targets.
provenanceNoOriginal provenance returned by still_resolve_artwork. Pass it unchanged with record to preserve source and UTC observation evidence.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
recordYes
statusYes
toolIdYes
resultsYes
versionYes
provenanceYes
schemaVersionYes
generatedAtUtcYes
sourceRecommendedCitationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / provenance
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Original provenance returned by still_resolve_artwork. Pass it unchanged with record to preserve source and UTC observation evidence.",
      +  "properties": {
      +    "metadataFetchedAtUtc": {
      +      "type": "string"
      +    },
      +    "method": {
      +      "enum": [
      +        "supplied_metadata",
      +        "source_api"
      +      ],
      +      "type": "string"
      +    },
      +    "objectId": {
      +      "type": "string"
      +    },
      +    "provider": {
      +      "type": "string"
      +    },
      +    "rawRights": {},
      +    "rightsCheckedAtUtc": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "scope": {
      +      "type": "string"
      +    },
      +    "sourceUrl": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "method",
      +    "sourceUrl",
      +    "rightsCheckedAtUtc"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • removedInput schema / properties / provenance
      Removed value: -{
      -  "additionalProperties": false,
      -  "description": "Original provenance returned by still_resolve_artwork. Pass it unchanged with record to preserve source and UTC observation evidence.",
      -  "properties": {
      -    "metadataFetchedAtUtc": {
      -      "type": "string"
      -    },
      -    "method": {
      -      "enum": [
      -        "supplied_metadata",
      -        "source_api"
      -      ],
      -      "type": "string"
      -    },
      -    "objectId": {
      -      "type": "string"
      -    },
      -    "provider": {
      -      "type": "string"
      -    },
      -    "rawRights": {},
      -    "rightsCheckedAtUtc": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "scope": {
      -      "type": "string"
      -    },
      -    "sourceUrl": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "method",
      -    "sourceUrl",
      -    "rightsCheckedAtUtc"
      -  ],
      -  "type": "object"
      -}
  3. Changed1 schema field changed
    • addedInput schema / properties / provenance
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Original provenance returned by still_resolve_artwork. Pass it unchanged with record to preserve source and UTC observation evidence.",
      +  "properties": {
      +    "metadataFetchedAtUtc": {
      +      "type": "string"
      +    },
      +    "method": {
      +      "enum": [
      +        "supplied_metadata",
      +        "source_api"
      +      ],
      +      "type": "string"
      +    },
      +    "objectId": {
      +      "type": "string"
      +    },
      +    "provider": {
      +      "type": "string"
      +    },
      +    "rawRights": {},
      +    "rightsCheckedAtUtc": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "scope": {
      +      "type": "string"
      +    },
      +    "sourceUrl": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "method",
      +    "sourceUrl",
      +    "rightsCheckedAtUtc"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnly, openWorld, idempotent, and non-destructive hints. The description adds meaningful behavioral context: 'Preserve warnings and separate sourceRecommendedCitation' and 'No image-use permission is granted'. These go beyond the annotations and clarify output handling and legal caveats.

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?

Four sentences with no filler. Purpose is front-loaded, followed by input mode, style constraint, and behavioral caveats. Every sentence earns its place.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high schema coverage and annotations, the description captures the essential operational constraints: exclusive input, style limit, preservation, and rights disclaimer. Output schema exists, so return values need no description. The still_resolve_artwork workflow is implied via the provenance field in the schema, so no gap is significant.

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 86%, so the schema does the heavy lifting. The description restates the mutual exclusivity of record/sourceUrl and the one-style-per-call rule, both already present in the schema. It does not add new parameter-level meaning beyond the schema, so a baseline of 3 is appropriate.

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?

The description states a specific action ('Format'), resource ('website/social credits, figure captions, Chicago 18, MLA 9 or APA 7'), and a distinguishing trait ('using the same engine as the STILL website'). It is clearly distinct from siblings still_get_capabilities and still_resolve_artwork.

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?

Provides explicit call constraints: 'Supply exactly one of record or supported sourceUrl' and 'One academic style per call'. It also notes the engine context. It doesn't explicitly name alternatives or exclusion conditions, but the schema's provenance field and sibling names make the workflow evident.

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