Modkeel

Do two mods work together

check_mod_pair

Read-onlyIdempotent

Whether two Minecraft mods ran together in the Modkeel lab, clashed, or were never tested together. Use it for "can I use X with Y?" or to check two suspects from diagnose_crash; for one mod's whole record, use get_mod_runs. Takes two mod ids in any order (from names, call search_mods first). Unknown ids are not an error: the verdict is untested, meaning no lab run, never a known conflict. With mc, only runs on that version count. clash wins if any run clashed. Returns the verdict and the runs behind it.

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": {
      "mod_a": "<mod_a>",
      "mod_b": "<mod_b>"
    },
    "name": "check_mod_pair"
  }
}

Input Schema

Name	Required	Description
`mc`	No	Minecraft version to narrow the answer to, e.g. 1.21.1, 1.20.1 or 26.2. Omit it to get every version the lab ran; with it, only runs on exactly that version count.
`mod_a`	Yes	First mod. Lowercase mod id as the loader knows it (the Modrinth/Fabric/NeoForge id, e.g. sodium, create, entityculling), not the display name. Unsure of the id? Call search_mods first.
`mod_b`	Yes	Second mod, same format, e.g. iris.

Output Schema

Name	Required	Description
`mc`	No
`data`	Yes	Snapshot date and license of the lab data; attribute when quoting.
`mods`	Yes
`runs`	Yes	The runs behind the verdict; env: server, client or clash.
`verdict`	Yes	untested: no lab run, not a known conflict.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026

TDQS

A4.5/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral context: unknown ids are not an error but yield an 'untested' verdict, mc narrows to exact-version runs, and clash takes precedence if any run clashed. However it does not describe the shape or size of the returned run list, so this is solid supplemental context rather than exhaustive.

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?

Front-loads the outcome definition, then prerequisites, semantics, and precedence rules, closing with the return summary. Sentences are dense but each carries distinct information; no repetition of annotation or schema content.

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

Completeness5/5

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

Covers the outcome vocabulary, the untested/unknown-id edge case, the version-narrowing parameter, ordering insensitivity, and precedence of clash, with an output schema handling return details. Nothing an agent needs to invoke or interpret this correctly appears to be missing.

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

Parameters4/5

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

Schema coverage is 100%, so parameter formats are already documented. The description nevertheless adds non-obvious semantics beyond the schema: the two ids are interchangeable ("any order"), ids may come from names via search_mods, and mc restricts to exactly one version. That exceeds the baseline for a fully covered schema.

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 names a specific verb-and-resource pair (compare whether two mods ran together) and enumerates the possible outcomes: worked together, clashed, or never tested. It also names the sibling it is not (get_mod_runs) for the one-mod case, so an agent can route between them without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit triggering scenarios ("can I use X with Y?", or two suspects from diagnose_crash) plus an explicit alternative (get_mod_runs for one mod's whole record) and a prerequisite (call search_mods first if unsure of ids). When-to-use, when-not, and alternatives are all present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Modkeel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?