Skip to main content
Glama
DanWahlin

Marvel MCP

by DanWahlin

get_comics_for_character

Retrieve Marvel comics featuring a specific character by providing the character ID and optional filters such as format, creators, events, or date range.

Instructions

Fetch Marvel comics filtered by character ID and optional filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
characterIdYes
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

  • The async handler that parses the input arguments using the schema, extracts characterId and passes remaining filters as query params to the Marvel Comics API endpoint for the character, and parses the response using ComicDataWrapperSchema.
    handler: async (args: any) => {
        const { characterId, ...rest } = GetComicsForCharacterSchema.parse(args);
        const res = await httpRequest(`/characters/${characterId}/comics`, serializeQueryParams(rest));
        return ComicDataWrapperSchema.parse(res);
    }
  • Input schema for the tool using Zod. Extends GetCharacterByIdSchema (providing required 'characterId') with numerous optional comic-specific filters like format, dates, titles, numbers, identifiers, sorting, and pagination.
    export const GetComicsForCharacterSchema = GetCharacterByIdSchema.extend({
      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(),
      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(),
    });
  • Exports the complete tool object for registration in the MCP system, including description, input schema reference, and handler implementation.
    export const get_comics_for_character = {
        description: `Fetch Marvel comics filtered by character ID and optional filters.`,
        schema: GetComicsForCharacterSchema,
        handler: async (args: any) => {
            const { characterId, ...rest } = GetComicsForCharacterSchema.parse(args);
            const res = await httpRequest(`/characters/${characterId}/comics`, serializeQueryParams(rest));
            return ComicDataWrapperSchema.parse(res);
        }
    };
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 lacks behavioral details. It doesn't disclose whether this is a read-only operation, potential rate limits, authentication needs, pagination behavior (implied by 'limit' and 'offset' parameters but not explained), or what the response format looks like (no output schema). The description only states the basic filtering capability.

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. Every word earns its place—no redundancy or fluff. It's appropriately sized for a tool with many parameters but could benefit from additional explanatory sentences.

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?

Given the high complexity (27 parameters, 0% schema coverage, no output schema, no annotations), the description is severely incomplete. It doesn't explain parameter usage, response format, error conditions, or behavioral constraints. For a tool with extensive filtering options, this minimal description leaves the agent guessing about implementation details.

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 fails to compensate for the massive documentation gap. It mentions 'optional filters' generically but doesn't explain any specific parameters (e.g., what 'dateDescriptor' or 'formatType' mean, how 'collaborators' should be formatted). The description adds minimal value beyond the schema's structure.

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 ('fetch'), resource ('Marvel comics'), and primary filter ('by character ID'). It distinguishes from siblings like 'get_comics' (which likely lacks character filtering) and 'get_comic_by_id' (which fetches a single comic). However, it doesn't explicitly differentiate from 'get_characters_for_comic' (which has an inverse relationship).

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 mentions 'optional filters' but provides no guidance on when to use this tool versus alternatives. It doesn't specify when to choose this over 'get_comics' (for broader searches) or 'get_comic_by_id' (for single comic details), nor does it mention prerequisites like needing a character ID from 'get_character_by_id' first.

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