Skip to main content
Glama
DanWahlin

Marvel MCP

by DanWahlin

get_characters

Retrieve Marvel character data with customizable filters such as name, comics, events, and series to streamline your API queries and data extraction.

Instructions

Fetch Marvel characters with optional filters

Input Schema

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

Implementation Reference

  • Tool registration and handler: defines the get_characters tool with description, input schema, and async handler that validates args, serializes query params, fetches from Marvel API /characters endpoint, and parses response using CharacterDataWrapperSchema.
    export const get_characters = {
        description: `Fetch Marvel characters with optional filters.`,
        schema: GetCharactersSchema,
        handler: async (args: any) => {
            const argsParsed = GetCharactersSchema.parse(args);
            const res = await httpRequest('/characters', serializeQueryParams(argsParsed));
            return CharacterDataWrapperSchema.parse(res);
        }
    };
  • Input schema (Zod) for get_characters tool, defining optional filters like name, limit, offset, etc., matching Marvel API character list parameters.
    export const GetCharactersSchema = z.object({
      name: z.string().optional(),
      nameStartsWith: z.string().optional(),
      modifiedSince: z.string().optional(),
      comics: 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(),
    });
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' which implies a read operation, but doesn't disclose behavioral traits such as rate limits, authentication needs, pagination behavior (implied by limit/offset but not explained), or what happens with invalid filters. For a tool with 10 parameters and no annotations, this is a significant gap.

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, with no redundancy or unnecessary elaboration. It's appropriately sized for a basic tool description.

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, 0% schema coverage, no annotations, no output schema), the description is inadequate. It doesn't explain parameter meanings, return values, error handling, or usage context. For a filtering tool with many options, more detail is needed to be complete.

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. It only mentions 'optional filters' generically without explaining any of the 10 parameters (e.g., what 'comics', 'events', 'orderBy' mean). This adds minimal value beyond the schema, failing to address the 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 ('Fetch') and resource ('Marvel characters'), and mentions optional filtering. However, it doesn't explicitly differentiate from sibling tools like 'get_character_by_id' or 'get_characters_for_comic', which would require a 5. The purpose is clear but lacks sibling distinction.

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_character_by_id' or 'get_characters_for_comic'. It mentions optional filters but doesn't specify scenarios or exclusions. This leaves the agent without clear usage context.

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