Skip to main content
Glama
DanWahlin

Marvel MCP

by DanWahlin

get_comics

Retrieve lists of Marvel comics based on customizable filters such as characters, creators, events, and publication details. Ideal for managing and accessing comic data efficiently.

Instructions

Fetches lists of Marvel comics with optional filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
charactersNo
collaboratorsNo
creatorsNo
dateDescriptorNo
dateRangeNo
diamondCodeNo
digitalIdNo
eanNo
eventsNo
formatNo
formatTypeNo
hasDigitalIssueNo
isbnNo
issnNo
issueNumberNo
limitNo
modifiedSinceNo
noVariantsNo
offsetNo
orderByNo
seriesNo
sharedAppearancesNo
startYearNo
storiesNo
titleNo
titleStartsWithNo
upcNo

Implementation Reference

  • Executes the get_comics tool: parses args, queries Marvel API /comics endpoint with optional filters, returns parsed comic data wrapper.
    handler: async (args: any) => {
        const argsParsed = GetComicsSchema.parse(args);
        const res = await httpRequest(`/comics`, serializeQueryParams(argsParsed));
        return ComicDataWrapperSchema.parse(res);
    }
  • Input schema (Zod) for get_comics tool, defining all optional query parameters for filtering Marvel comics.
    export const GetComicsSchema = z.object({
      format: z.string().optional(),
      formatType: z.string().optional(),
      noVariants: z.boolean().optional(),
      dateDescriptor: z.string().optional(),
      dateRange: z.string().optional(),
      title: z.string().optional(),
      titleStartsWith: z.string().optional(),
      startYear: z.number().optional(),
      issueNumber: z.number().optional(),
      diamondCode: z.string().optional(),
      digitalId: z.number().optional(),
      upc: z.string().optional(),
      isbn: z.string().optional(),
      ean: z.string().optional(),
      issn: z.string().optional(),
      hasDigitalIssue: z.boolean().optional(),
      modifiedSince: z.string().optional(),
      creators: z.string().optional(),
      characters: z.string().optional(),
      series: z.string().optional(),
      events: z.string().optional(),
      stories: z.string().optional(),
      sharedAppearances: z.string().optional(),
      collaborators: z.string().optional(),
      orderBy: z.string().optional(),
      limit: z.number().min(1).max(100).optional(),
      offset: z.number().optional(),
    });
  • Tool definition and registration export for get_comics, including description, input schema reference, and handler function.
    export const get_comics = {
        description: `Fetches lists of Marvel comics with optional filters.`,
        schema: GetComicsSchema,
        handler: async (args: any) => {
            const argsParsed = GetComicsSchema.parse(args);
            const res = await httpRequest(`/comics`, serializeQueryParams(argsParsed));
            return ComicDataWrapperSchema.parse(res);
        }
    };
  • Shared output schema used by get_comics handler to parse the Marvel API response for comic lists.
    export const ComicDataWrapperSchema = z.object({
      code: z.number(),
      status: z.string(),
      copyright: z.string(),
      attributionText: z.string(),
      attributionHTML: z.string(),
      data: ComicDataContainerSchema,
      etag: z.string(),
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'fetches' with 'optional filters.' It doesn't disclose whether this is a read-only operation, pagination behavior (despite limit/offset parameters), rate limits, authentication requirements, error conditions, or what the return format looks like (no output schema).

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?

The description is a single, efficient sentence that front-loads the core purpose. There's no wasted language or redundancy, making it appropriately concise for a tool with many parameters.

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

Completeness2/5

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

For a complex tool with 27 parameters, no annotations, and no output schema, the description is severely incomplete. It doesn't explain the tool's behavior, parameter usage, return format, or how it relates to sibling tools, leaving critical gaps for an agent to understand and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 27 parameters and 0% schema description coverage, the description provides no parameter semantics beyond 'optional filters.' It doesn't explain what any parameter does, their formats (e.g., dateRange format), relationships, or default values. The description fails to compensate for the massive schema coverage gap.

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 clearly states the action ('fetches lists') and resource ('Marvel comics') with the scope of optional filtering. It distinguishes from siblings like 'get_comic_by_id' (single comic) and 'get_comics_for_character' (character-specific), but doesn't explicitly differentiate from other list tools like 'get_characters'.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_comic_by_id' for single comics or 'get_comics_for_character' for character-specific comics. It mentions optional filters but doesn't explain when specific filters are appropriate or what the default behavior is.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DanWahlin/marvel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server