Skip to main content
Glama

search_spells

Search D&D 5e SRD spells by name, level, school, class, concentration, ritual, components, damage type, or save type.

Instructions

Search D&D 5e SRD spells by name, level, school, class, concentration, ritual, components, damage type, or save type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch term for spell name or description
levelNoSpell level (0 for cantrips, 1-9 for leveled spells)
schoolNoSchool of magic (e.g. "evocation", "necromancy")
class_nameNoSpellcasting class (e.g. "Wizard", "Cleric")
concentrationNoFilter by concentration requirement
ritualNoFilter by ritual casting
has_materialNoFilter by material component requirement
damage_typeNoDamage type (e.g. "fire", "necrotic", "radiant")
save_typeNoSaving throw type (e.g. "DEX", "WIS", "CON")
limitNoResults per page (max 50)
offsetNoOffset for pagination

Implementation Reference

  • Registration and handler function for the 'search_spells' tool. Registers the tool with an MCP server, defines its schema (query, level, school, class_name, concentration, ritual, has_material, damage_type, save_type, limit, offset), and implements the handler that calls searchSpells in the DB layer and formats results using formatSpell.
    export function registerSearchSpells(
      server: McpServer,
      db: Database.Database,
    ): void {
      server.registerTool(
        'search_spells',
        {
          description:
            'Search D&D 5e SRD spells by name, level, school, class, concentration, ritual, components, damage type, or save type.',
          inputSchema: {
            query: z.string().optional().describe('Search term for spell name or description'),
            level: z.number().min(0).max(9).optional().describe('Spell level (0 for cantrips, 1-9 for leveled spells)'),
            school: z.string().optional().describe('School of magic (e.g. "evocation", "necromancy")'),
            class_name: z.string().optional().describe('Spellcasting class (e.g. "Wizard", "Cleric")'),
            concentration: z.boolean().optional().describe('Filter by concentration requirement'),
            ritual: z.boolean().optional().describe('Filter by ritual casting'),
            has_material: z.boolean().optional().describe('Filter by material component requirement'),
            damage_type: z.string().optional().describe('Damage type (e.g. "fire", "necrotic", "radiant")'),
            save_type: z.string().optional().describe('Saving throw type (e.g. "DEX", "WIS", "CON")'),
            limit: z.number().min(1).max(50).default(10).describe('Results per page (max 50)'),
            offset: z.number().min(0).default(0).describe('Offset for pagination'),
          },
        },
        async ({
          query,
          level,
          school,
          class_name,
          concentration,
          ritual,
          has_material,
          damage_type,
          save_type,
          limit,
          offset,
        }) => {
          const result = searchSpells(db, {
            query,
            level,
            school,
            class_name,
            concentration,
            ritual,
            has_material,
            damage_type,
            save_type,
            limit,
            offset,
          });
    
          if (result.rows.length === 0) {
            return {
              content: [
                {
                  type: 'text' as const,
                  text: 'No spells found matching your criteria. Try a broader search — for example, remove some filters or use a partial name.',
                },
              ],
              isError: true,
            };
          }
    
          const start = (offset ?? 0) + 1;
          const end = (offset ?? 0) + result.rows.length;
          const header = `Found ${result.total} spell${result.total === 1 ? '' : 's'} (showing ${start}-${end})\n`;
    
          const spells = result.rows.map(formatSpell).join('\n\n---\n\n');
    
          return {
            content: [{ type: 'text' as const, text: header + '\n' + spells }],
          };
        },
      );
    }
  • Input schema for the search_spells tool, defined inline in the registerTool call using Zod. All fields are optional except limit and offset which have defaults.
    inputSchema: {
      query: z.string().optional().describe('Search term for spell name or description'),
      level: z.number().min(0).max(9).optional().describe('Spell level (0 for cantrips, 1-9 for leveled spells)'),
      school: z.string().optional().describe('School of magic (e.g. "evocation", "necromancy")'),
      class_name: z.string().optional().describe('Spellcasting class (e.g. "Wizard", "Cleric")'),
      concentration: z.boolean().optional().describe('Filter by concentration requirement'),
      ritual: z.boolean().optional().describe('Filter by ritual casting'),
      has_material: z.boolean().optional().describe('Filter by material component requirement'),
      damage_type: z.string().optional().describe('Damage type (e.g. "fire", "necrotic", "radiant")'),
      save_type: z.string().optional().describe('Saving throw type (e.g. "DEX", "WIS", "CON")'),
      limit: z.number().min(1).max(50).default(10).describe('Results per page (max 50)'),
      offset: z.number().min(0).default(0).describe('Offset for pagination'),
    },
  • Database query helper that builds a dynamic SQL query from optional filters. Supports full-text search via FTS5 (spells_fts), filtering by level, school, class_name, concentration, ritual, has_material, damage_type, save_type, and pagination via limit/offset. Returns typed SearchResult with rows and total count.
    export function searchSpells(
      db: Database.Database,
      filters: SpellFilters,
    ): SearchResult<SpellRow> {
      const conditions: string[] = [];
      const params: (string | number)[] = [];
    
      if (filters.query) {
        const ftsQuery = sanitizeFtsQuery(filters.query);
        if (ftsQuery.length > 0) {
          conditions.push(
            's.id IN (SELECT rowid FROM spells_fts WHERE spells_fts MATCH ?)',
          );
          params.push(ftsQuery);
        }
      }
    
      if (filters.level !== undefined) {
        conditions.push('s.level = ?');
        params.push(filters.level);
      }
    
      if (filters.school) {
        conditions.push('LOWER(s.school) = LOWER(?)');
        params.push(filters.school);
      }
    
      if (filters.class_name) {
        conditions.push('LOWER(s.classes) LIKE LOWER(?)');
        params.push(`%${filters.class_name}%`);
      }
    
      if (filters.concentration !== undefined) {
        conditions.push('s.concentration = ?');
        params.push(filters.concentration ? 1 : 0);
      }
    
      if (filters.ritual !== undefined) {
        conditions.push('s.ritual = ?');
        params.push(filters.ritual ? 1 : 0);
      }
    
      if (filters.has_material !== undefined) {
        conditions.push('s.components_m = ?');
        params.push(filters.has_material ? 1 : 0);
      }
    
      if (filters.damage_type) {
        conditions.push('LOWER(s.damage_type) = LOWER(?)');
        params.push(filters.damage_type);
      }
    
      if (filters.save_type) {
        conditions.push('LOWER(s.save_type) = LOWER(?)');
        params.push(filters.save_type);
      }
    
      const where =
        conditions.length > 0 ? `WHERE ${conditions.join(' AND ')}` : '';
      const limit = filters.limit ?? 20;
      const offset = filters.offset ?? 0;
    
      const countRow = db
        .prepare(`SELECT COUNT(*) as count FROM spells s ${where}`)
        .get(...params) as { count: number };
    
      const rows = db
        .prepare(
          `SELECT s.* FROM spells s ${where} ORDER BY s.level ASC, s.name ASC LIMIT ? OFFSET ?`,
        )
        .all(...params, limit, offset) as SpellRow[];
    
      return { rows, total: countRow.count };
    }
  • Helper function that formats a SpellRow into a Markdown string including name (h2), level/school, tags (concentration/ritual), casting time, range, components, duration, description, higher levels, damage type, save, and classes.
    function formatSpell(spell: SpellRow): string {
      const lines: string[] = [];
    
      lines.push(`## ${spell.name}`);
    
      const schoolStr = spell.school.charAt(0).toUpperCase() + spell.school.slice(1);
      const levelStr = levelLabel(spell.level);
      const tags: string[] = [];
      if (spell.concentration) tags.push('concentration');
      if (spell.ritual) tags.push('ritual');
      const tagStr = tags.length > 0 ? ` (${tags.join(', ')})` : '';
    
      if (spell.level === 0) {
        lines.push(`*${schoolStr} cantrip${tagStr}*`);
      } else {
        lines.push(`*${levelStr} ${schoolStr.toLowerCase()}${tagStr}*`);
      }
      lines.push('');
    
      lines.push(`**Casting Time:** ${spell.casting_time}`);
      lines.push(`**Range:** ${spell.range}`);
      lines.push(`**Components:** ${formatComponents(spell)}`);
      lines.push(`**Duration:** ${spell.duration}`);
      lines.push('');
    
      lines.push(spell.description);
    
      if (spell.higher_level) {
        lines.push('');
        lines.push(`**At Higher Levels.** ${spell.higher_level}`);
      }
    
      if (spell.damage_type) {
        lines.push('');
        lines.push(`**Damage Type:** ${spell.damage_type}`);
      }
    
      if (spell.save_type) {
        lines.push(`**Save:** ${spell.save_type}`);
      }
    
      lines.push('');
      lines.push(`**Classes:** ${formatClasses(spell.classes)}`);
    
      return lines.join('\n');
    }
  • src/server.ts:47-47 (registration)
    Registration call in the main server file. The registerSearchSpells function is imported from './tools/search-spells.js' and called during server initialization.
    registerSearchSpells(server, db);
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It names filter options but fails to detail how filters interact, pagination behavior, or response format, leaving significant gaps for an 11-parameter search tool.

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, well-structured sentence that conveys all key filtering dimensions without any redundancy or unnecessary words.

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?

Despite having 11 parameters and no output schema, the description is too brief. It omits critical context such as how filters combine, result sorting, pagination details, and error handling, which are essential for correct tool invocation.

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?

With 100% schema description coverage, the schema already explains all parameters. The description lists the same filters but adds no new semantics or constraints beyond what is in the schema, so it is adequate but not additive.

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 clearly states the tool searches 'D&D 5e SRD spells' and lists specific filtering criteria (name, level, school, etc.), making the purpose immediately obvious.

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

Usage Guidelines3/5

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

The description implies usage for searching spells but lacks explicit guidance on when to use this tool versus siblings like search_monsters or search_equipment, or any exclusions.

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

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/gregario/dnd-oracle'

If you have feedback or need assistance with the MCP directory API, please join our Discord server