What a mod is, from its catalog page
get_mod_infoWhat one Minecraft mod is and where to get it: its Modrinth page (title, summary, categories, loaders, the Minecraft releases its author lists, client/server side, licence, downloads, source and issue links) next to a short Modkeel lab record (tested versions, run and pair counts). Use it for "what does this mod do?", "is it client-only?", "where do I download it?" or to link a suspect from diagnose_crash. The versions here are what the author declares; for what the lab saw run or crash, use get_mod_runs, and for two mods together, check_mod_pair. Takes a lab mod id or a Modrinth slug; from a name, call search_mods first. The project is matched by the SHA-1 of a jar the lab ran (source: jar_hash, exact), else by slug (source: slug); a mod on neither returns found: false, not an error. Asks Modrinth live on each call (nothing cached here), so it can fail when Modrinth is down: retry later.
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_id": "<mod_id>"
},
"name": "get_mod_info"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mod_id | Yes | Lab mod id (e.g. fabric_api, ferritecore) or Modrinth slug (e.g. fabric-api, sodium-extra), lowercase. Unsure? Call search_mods first. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lab | Yes | ||
| mod | Yes | ||
| data | Yes | Snapshot date and license of the lab data; attribute when quoting. | |
| found | Yes | False: on neither Modrinth nor in lab jars. | |
| source | No | How the Modrinth project was matched. | |
| modrinth | Yes | ||
| other_projects | No | Other Modrinth project ids for this mod id: a fork the lab also ran, or the project whose slug is this id when the lab ran a port (fabric_api on NeoForge). |