Skip to main content
Glama
j4th
by j4th

tribal_staples

Read-onlyIdempotent

Retrieve top cards for a creature type, grouped into lords, synergy pieces, and key members. Supports color and format filters for targeted deck building.

Instructions

Best cards for a creature type — lords, synergy pieces, and top members.

Groups results by: lords/anthems, tribal synergy, best members, tribal support.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tribeYesCreature type (e.g. 'Goblin', 'Merfolk', 'Samurai')
color_identityNoColor identity filter (e.g. 'sultai', 'WR')
formatNoFormat legality filter (e.g. 'commander', 'modern')
limitNoMaximum number of results
response_formatNoOutput verbosity: 'detailed' (default) or 'concise'detailed
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds valuable context on how results are grouped (lords/anthems, tribal synergy, etc.), which is beyond what annotations provide. No contradictions.

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?

Two sentences, front-loaded with the action and resource, zero waste. Every word earns its place.

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?

With 100% schema coverage and annotations, the description effectively conveys purpose and grouping. It lacks examples or mention of return format, but is largely complete for a staple-finding tool.

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 parameters are well-documented. The description does not add new meaning to parameters; it only describes output grouping. Baseline 3 is appropriate.

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 it returns the best cards for a creature type, grouped by categories like lords, synergy pieces, etc. This is specific and distinct from sibling tools like color_identity_staples.

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 when needing tribal staples, but does not explicitly state when to use this tool over alternatives like goldfish_format_staples or color_identity_staples, nor does it provide when-not-to-use guidance.

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/j4th/mtg-mcp-server'

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