Skip to main content
Glama
Sign In
Cavalera Forge MCP

Cavalera Forge MCP

by jbillochon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Missions rewarding a product

product_missions
Read-onlyIdempotent

Find Star Citizen missions that reward a specific product, blueprint, or item, sorted by payout and showing faction, system, reward, and required standing.

Instructions

Missions that can reward this product (blueprint or item), best paid first: type, faction, systems, reward, required standing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "product_missions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
productNoProduct name.
product_idNoExact product id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior. The description adds useful non-annotation context: results are ordered 'best paid first', accepted product inputs include blueprints or items, and the returned fields are enumerated. It does not discuss pagination or rate limits, but it exceeds the minimum given annotation coverage.

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 a single front-loaded sentence with no wasted clauses. It packs purpose, ordering, accepted input type, and returned fields into a compact form.

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 no output schema, enumerating returned fields is valuable. However, all three parameters are optional, and the description does not explain what happens if neither product nor product_id is supplied, nor how limit is applied. These are meaningful gaps for correct invocation.

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 description coverage is moderate at 67%, with product and product_id minimally described and limit undocumented. The description adds meaningful value by saying the product can be a blueprint or item, but it does not clarify how product and product_id relate or how limit affects results.

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 first clause states a specific resource relationship: missions that can reward this product, and the description also lists sort order and returned fields. It is clear what the tool returns, though it does not explicitly differentiate itself from sibling tools such as product_recipe or craftable_from.

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 implied by the phrase 'Missions that can reward this product', but there is no explicit when-to-use guidance, no alternatives named, and no explanation of when to use product versus product_id. The agent can infer the general purpose, but must still guess at selection conditions.

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