Skip to main content
Glama
Sign In
Cavalera Forge MCP

Cavalera Forge MCP

by jbillochon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Mineral card

mineral_info
Read-onlyIdempotent

Retrieve complete mineral data for Star Citizen mining: locations, scan signatures, extraction profiles, quality bands, refinery rankings, and terminal sell prices by mineral.

Instructions

Everything about a mineral: best mining locations, scan signature per rock and method, extraction profile (resistance, instability, optimal window, explosion), quality bands, best and worst refineries, best terminal sell prices.

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": {
      "mineral": "<mineral>"
    },
    "name": "mineral_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
mineralYesMineral or ore, e.g. 'Quantainium', 'Stileron (Raw)', 'Ice'.
locationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds valuable context by enumerating exactly what data is returned (best mining locations, scan signatures, extraction profile details, refineries, terminal prices), which is beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence that front-loads the core purpose and then lists included data without wasteful words. It could be better structured with bullets, but it is appropriately sized for a comprehensive info tool.

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?

For a read-only info tool with no output schema, the description does a good job of specifying return content. However, it leaves two notable gaps: it does not explain the locations parameter, and it does not distinguish this aggregated tool from several sibling tools that provide overlapping data.

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

Parameters2/5

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

Schema coverage is 50%: the mineral parameter is documented with examples, but the locations parameter (integer, default 8, max 30) has no description. The tool description mentions 'best mining locations' but does not explain how the locations parameter affects the output or its default/maximum values.

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 clearly states it provides comprehensive information about a mineral, listing specific data categories (mining locations, scan signature, extraction profile, etc.). However, it does not explicitly differentiate itself from siblings like mining_locations, identify_signature, refinery_yields, or terminal_prices, which cover subsets of the same data.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the many sibling tools that overlap (e.g., mining_locations, refinery_yields, terminal_prices). The description implies usage for full detail but offers no exclusions or alternatives.

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