Skip to main content
Glama
DanWahlin

Marvel MCP

by DanWahlin

get_comic_by_id

Retrieve detailed information about a specific Marvel comic using its unique ID through the Marvel MCP server.

Instructions

Fetch a single Marvel comic by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comicIdYes

Implementation Reference

  • The handler function that parses the input arguments, fetches the comic data via HTTP request using the provided comicId, parses the response with ComicDataWrapperSchema, and returns it.
    handler: async (args: any) => {
        const argsParsed = GetComicByIdSchema.parse(args);
        const res = await httpRequest(`/comics/${argsParsed.comicId}`);
        return ComicDataWrapperSchema.parse(res);
    }
  • Zod schema defining the input parameters for the tool: a required numeric comicId.
    export const GetComicByIdSchema = z.object({
      comicId: z.number(),
    });
  • The tool registration exporting the get_comic_by_id tool object with description, input schema, and handler function.
    export const get_comic_by_id = {
        description: `Fetch a single Marvel comic by ID.`,
        schema: GetComicByIdSchema,
        handler: async (args: any) => {
            const argsParsed = GetComicByIdSchema.parse(args);
            const res = await httpRequest(`/comics/${argsParsed.comicId}`);
            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 the full burden of behavioral disclosure. It states the tool fetches data, implying a read-only operation, but doesn't address critical aspects like authentication needs, rate limits, error handling, or what happens with invalid IDs. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 extremely concise—a single sentence with no wasted words—and front-loads the key information ('Fetch a single Marvel comic by ID'). Every word earns its place, making it easy to parse quickly.

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 tool's simplicity (one parameter, no output schema) and lack of annotations, the description is incomplete. It doesn't cover behavioral traits (e.g., error cases), parameter details, or output expectations, leaving the agent with insufficient context to use the tool effectively beyond its basic purpose.

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?

The schema description coverage is 0%, but the description adds minimal semantic context by specifying that the parameter 'comicId' is used to fetch a single comic. However, it doesn't clarify the format (e.g., numeric ID), valid ranges, or examples, which is insufficient to fully compensate for the lack of schema documentation. The baseline is adjusted upward due to only one parameter.

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 resource ('a single Marvel comic by ID'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_comics' (which likely fetches multiple comics), leaving room for minor ambiguity about when to choose this specific tool.

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_comics' or 'get_comics_for_character'. It lacks context about prerequisites (e.g., needing a valid comic ID) or exclusions, leaving the agent to infer usage from the tool name alone.

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