LectureForge MCP

get_artifact

Fetch safe metadata and resource/file URIs for one generated artifact, including PowerPoint, source bundle, IR, manifest, validation, or Python source.

Instructions

Get safe metadata and resource/file URIs for one generated artifact.

Artifact choices are powerpoint, source_bundle, presentation_ir, manifest, validation, and python_source.

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": {
      "project_id": "<project_id>",
      "artifact": "<artifact>"
    },
    "name": "get_artifact"
  }
}

Input Schema

Name	Required	Default
`version`	No	latest
`artifact`	Yes
`project_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Sep 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only lookup via 'safe metadata' but never states that nothing is mutated, nor does it cover auth requirements, availability of a missing artifact, or the 'latest' default resolution behavior. With zero annotation coverage this is thin.

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 short, front-loaded sentences with no filler; the core purpose leads and the enumeration supports it. The list formatting is slightly awkward but costs nothing in comprehension.

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?

An output schema exists, so return-value shape need not be described. For a 3-parameter lookup tool this is roughly adequate, but the absence of annotations plus undocumented project_id/version semantics leaves gaps an agent may hit when constructing a call.

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%, so the description must compensate. It does so well for the critical 'artifact' parameter by enumerating the six valid choices, which the schema lacks as an enum, but it says nothing about project_id or the version parameter (including how 'latest' is resolved).

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 verb and resource ('Get safe metadata and resource/file URIs for one generated artifact') and enumerates the artifact kinds, so an agent knows exactly what comes back. It does not, however, differentiate itself from siblings like get_presentation_ir or list_versions, leaving the boundary to inference.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative, even though get_presentation_ir and list_versions are plausible competing entry points. The artifact enumeration implies the tool is the entry point for any artifact type, but that is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server