Skip to main content
Glama
Sign In
Cavalera Forge MCP

Cavalera Forge MCP

by jbillochon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Search craftable products

search_products
Read-onlyIdempotent

Find craftable products by name with typo tolerance. Filter results by product type, set a limit, or list available types and subtypes.

Instructions

Find craftable products by name (typo tolerant).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesPart of a product name, e.g. 'Pembroke', 'Arrowhead'.
list_typesNoReturn the product types and subtypes instead.
product_typeNoOptional type filter: armour, weapons, ammo, cooler, powerplant, quantumdrive, shield, radar, mininglaser, miningmodule, tractorbeam, salvage, refuelling, orepod. Call with list_types=true to see all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description contributes one genuine behavioral trait beyond them — typo-tolerant matching — but says nothing about result ordering, what the default limit of 15 means in practice, or that craftable scope excludes non-craftable items.

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?

A single short sentence, front-loaded with the verb and resource, with the qualifier in parentheses where it belongs. No filler or restated structure.

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

Completeness3/5

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

With annotations and a reasonably documented schema, the description is adequate for a simple 4-param read tool, but it omits the fact that list_types=true changes the return shape entirely (types/subtypes instead of products) and gives no hint about the relation to product_recipe or craftable_from for follow-up calls.

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 75% with strong inline docs on query ('Pembroke', 'Arrowhead'), product_type (full enum list), and list_types, so the schema carries most of the burden. The description itself adds no parameter meaning beyond 'by name' being the query field; limit is undocumented in both places but bounded 1-50 with a default.

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 states a specific verb and resource (Find craftable products) plus the matching mode (by name, typo tolerant), so the agent knows exactly what is searched. It does not, however, differentiate this from siblings like marketplace_search, marketplace_find_items, or craftable_from, which are also product/item lookup tools.

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?

Usage is only implied: 'find ... by name' suggests free-text lookup, but nothing states when to prefer this over marketplace_search or craftable_from, nor when to use the list_types mode. The agent must infer routing from sibling names alone.

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