Skip to main content
Glama
DanWahlin

Marvel MCP

by DanWahlin

get_characters_for_comic

Retrieve Marvel characters associated with a specific comic by providing the comic ID. Ideal for developers and fans exploring character details in the Marvel MCP server.

Instructions

Fetch Marvel characters for a given comic

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comicIdYes
eventsNo
limitNo
modifiedSinceNo
nameNo
nameStartsWithNo
offsetNo
orderByNo
seriesNo
storiesNo

Implementation Reference

  • The handler function that parses input arguments using the schema, makes an HTTP request to the Marvel API endpoint for characters in a specific comic, and parses the response using CharacterDataWrapperSchema.
    handler: async (args: any) => {
        const { comicId, ...rest } = GetComicCharactersSchema.parse(args);
        const res = await httpRequest(`/comics/${comicId}/characters`, serializeQueryParams(rest));
        return CharacterDataWrapperSchema.parse(res);
    }
  • Zod schema defining the input parameters for the get_characters_for_comic tool, extending GetComicByIdSchema with additional optional filters for characters.
    export const GetComicCharactersSchema = GetComicByIdSchema.extend({
      name: z.string().optional(),
      nameStartsWith: z.string().optional(),
      modifiedSince: z.string().optional(),
      series: z.string().optional(),
      events: z.string().optional(),
      stories: z.string().optional(),
      orderBy: z.string().optional(),
      limit: z.number().min(1).max(100).optional(),
      offset: z.number().optional(),
    });
  • Exports the tool definition object including description, input schema, and handler function, likely used for MCP tool registration.
    export const get_characters_for_comic = {
        description: `Fetch Marvel characters for a given comic.`,
        schema: GetComicCharactersSchema,
        handler: async (args: any) => {
            const { comicId, ...rest } = GetComicCharactersSchema.parse(args);
            const res = await httpRequest(`/comics/${comicId}/characters`, serializeQueryParams(rest));
            return CharacterDataWrapperSchema.parse(res);
        }
    };
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Fetch' (implying a read operation) but doesn't disclose behavioral traits like pagination (offset/limit parameters), rate limits, authentication needs, error conditions, or response format. The description adds minimal context beyond the basic action.

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?

Extremely concise single sentence with zero waste. It's front-loaded with the core purpose and efficiently communicates the essential action and target.

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 complexity (10 parameters, 1 required), lack of annotations, and no output schema, the description is incomplete. It doesn't address parameter usage, behavioral expectations, or return values, making it inadequate for a tool with this many undocumented parameters and no structured guidance.

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?

Schema description coverage is 0%, so the description must compensate but doesn't. It mentions 'for a given comic' which hints at the required 'comicId', but doesn't explain the purpose of the other 9 parameters (e.g., 'events', 'modifiedSince', 'orderBy'). This leaves most parameters undocumented in both schema and description.

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') and target resource ('Marvel characters for a given comic'), distinguishing it from siblings like 'get_characters' (general character list) and 'get_comics_for_character' (reverse relationship). However, it doesn't specify the exact scope (e.g., all characters appearing in that comic vs. filtered subset).

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?

No explicit guidance on when to use this tool versus alternatives like 'get_characters' or 'get_character_by_id'. The description implies usage for comic-specific character queries but doesn't mention prerequisites, limitations, or comparative scenarios with sibling tools.

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