Skip to main content
Glama
Niclasp1501

ninjos-foundry-mcp

by Niclasp1501
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List DSA5 archetypes

list-dsa5-archetypes
Read-onlyIdempotent

Find DSA5 archetypes in actor compendiums, filter by species or profession, and create a hero from the results.

Instructions

[DSA5 only] Find archetypes (ready made heroes of type character) in the actor compendiums of the dsa5 system, e.g. from the DSA5 core rules module, to create a hero with create-dsa5-character-from-archetype. Each archetype comes with id, name, compendium, species, profession and image. filterBySpecies matches the whole species ignoring case, filterByProfession a part of the profession ignoring case. A compendium that cannot be read is named with its cause.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packIdNoSearch only this actor compendium, e.g. "dsa5-core.corearchetypes". Without it every actor compendium of the dsa5 system is searched.
filterBySpeciesNoKeep archetypes of exactly this species, ignoring case, e.g. "Mensch" or "Zwerg"
filterByProfessionNoKeep archetypes whose profession contains this text, ignoring case, e.g. "Magier"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv14.2609.4

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable behavioral detail beyond that: the returned fields are listed, filter behavior is specified, and failed compendium reads are reported with their cause.

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 compact and front-loaded. Every sentence earns its place: scope, purpose, output fields, filter semantics, and error behavior are each covered without redundancy or fluff.

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

Completeness5/5

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

For a read-only list tool with no required parameters and no output schema, the description provides enough context to call it correctly: output shape, filter semantics, default search scope, and failure behavior are all documented.

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?

Schema coverage is 100%, so the parameter descriptions already document packId, filterBySpecies, and filterByProfession. The tool description mostly restates the matching semantics already present in the schema, so it adds little new parameter-level meaning.

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 states a specific action and resource: 'Find archetypes' in 'the actor compendiums of the dsa5 system'. It also clarifies what an archetype is and connects the tool to its intended downstream use with create-dsa5-character-from-archetype, making it distinguishable from generic list tools.

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

Usage Guidelines4/5

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

The description gives clear usage context: it is for DSA5 only and is meant to find archetypes to feed into create-dsa5-character-from-archetype. It does not explicitly enumerate alternatives or when-not-to-use cases, but the intended workflow is well established.

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

Deploy Server

Other Tools