Skip to main content
Glama
Sign In
Cavalera Forge MCP

Cavalera Forge MCP

by jbillochon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Mining locations

mining_locations
Read-onlyIdempotent

Find where a mineral is mined in Star Citizen: returns places, systems, deposit methods and concentration ranges, most frequent first; if no match, lists minerals.

Instructions

Where a mineral is found, most frequent first: place, system, place type, method (ship, ROC, FPS), share of deposits and concentration range. Without a name match, lists the minerals.

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": "mining_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
systemNoOptional: Stanton, Pyro, Nyx.
mineralYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world semantics, so the bar is lower. The description still adds non-trivial behavior: results are sorted most-frequent-first, the share/concentration fields are ranges, and a no-match lookup degrades into a mineral list rather than erroring.

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?

Two compact sentences with the ordering rule front-loaded and the fallback behavior second. Slightly dense field enumeration but every clause carries information.

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 no output schema, the description helpfully enumerates the return fields and their ordering, which is exactly what an agent needs. The main gap is the undocumented 'limit' parameter and any note on units or typical result sizes.

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 only 33% (only 'system' is documented), so the description must compensate. It clarifies that 'mineral' is a name lookup with a listing fallback, but says nothing about 'limit' (default 15, max 100) or how results are capped/ordered beyond 'most frequent first'.

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 the resource concretely: where a mineral is found, ordered by frequency, with the exact fields returned (place, system, place type, method, deposit share, concentration range). It also describes the fallback ('Without a name match, lists the minerals'). It stops short of naming how it differs from siblings like mineral_info or list_minerals.

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 explicit when-to-use or when-not-to-use guidance, and no reference to the many plausible alternatives (mineral_info, list_minerals, identify_signature). The only directional signal is an implicit fallback behavior, not a usage instruction.

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