Skip to main content
Glama
Sign In

Comicvine

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search

search
Read-onlyIdempotent

Comic Vine — search the comic-book reference database (characters, issues, volumes, publishers, creators, story arcs) by name. Resource list: character, concept, issue, location, object, person, publisher, story_arc, team, volume. Use ONLY for fictional comic-book entities — Marvel, DC, indie comics, manga. NOT for machine learning / ML / AI research (use arxiv_search_papers) or real-world events.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "Spider-Man"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
queryYes
resourcesNoComma-sep resource types.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "Spider-Man"
+  },
+  {
+    "limit": 10,
+    "page": 1,
+    "query": "Batman",
+    "resources": "character,issue"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Multi-resource search results from Comic Vine API",
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds minimal behavioral context beyond 'search by name' and does not address pagination or rate limits. It does not contradict annotations.

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 two concise sentences, front-loaded with the core purpose and followed by key restrictions. No redundant or vague phrasing.

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

Completeness4/5

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

Given the tool's complexity (4 parameters, output schema present) and sibling tools for specific resources, the description covers domain, usage, and exclusions adequately. It does not explain output format, but the output schema compensates.

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

Parameters4/5

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

Schema description coverage is low (25%), but the description adds meaning for 'query' (search by name) and 'resources' (lists possible types: character, concept, etc.). However, 'page' and 'limit' lack additional context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states it searches a comic-book reference database by name and lists resource types. It distinguishes from siblings by specifying the domain (comic books) and excluding ML research and real-world events, making the purpose unequivocal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly states when to use (comic-book entities) and when not to use (ML research, real-world events), with explicit alternative tools like arxiv_search_papers provided.

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

All Comicvine toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources