Skip to main content
Glama
Sign In

Xodia

by ai.xodia
OverviewDiscussionsAdmin

Get skill

get_skill
Read-only

Returns one of Xodia's skills (step-by-step instructions for a kind of work) for the project you are working on: core skills, plus the stack packs get_project lists for that project. Requests, prompts and the router name the skills and packs to follow; load each one when you start the work it covers, once per conversation, not ahead of time. Some skills end with a References list of longer detail: pass ref with one of those names only when the task needs it. tailwind-upgrade load without a projectId, for work before the site is in Xodia (tailwind-upgrade: a repo refused with tailwind3_unsupported). Skills are licensed to the workspace for use in Xodia: use them for the task, never copy, save or export them.

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

Input Schema

NameRequiredDescriptionDefault
refNoA reference from the skill's References list, such as typography for design-system. Leave out to load the skill itself.
nameYesSkill name, such as edit-safely
projectIdNoThe project you are working on (from list_projects or the request). Required except for tailwind-upgrade

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, non-open-world), yet the description still adds real behavior: a once-per-conversation load discipline, a rule that skills come from requests/prompts/router rather than being pre-fetched, and a licensing restriction (never copy, save or export). What it omits is the shape and size of the returned payload and whether refs have their own limits, which keeps it off a 5.

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 load-when-you-start rule is front-loaded and most sentences carry distinct information. The tailwind-upgrade clause is compressed into near-unparseable shorthand ("tailwind-upgrade load without a projectId ... (tailwind-upgrade: a repo refused with tailwind3_unsupported)"), which costs clarity for the space it saves.

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 3 parameters, a 74-value enum, no output schema and annotations in place, the description covers enough: what is returned, when to load it, how ref works, and the legal restriction on reuse. Missing is any indication of skill length or what happens when a ref name does not exist in a skill's References list.

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 100%, so the baseline is 3. The description's statements about ref (References list) and projectId (tailwind-upgrade exception) largely restate what the schema already documents, adding only light framing about calling ref when the task needs the detail.

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?

"Returns one of Xodia's skills (step-by-step instructions for a kind of work) for the project you are working on" gives a specific verb and resource and even defines the resource for an agent that has never seen it. It also scopes the content (core skills plus the stack packs get_project lists), so no sibling tool could be confused with it.

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?

Timing is explicit: "load each one when you start the work it covers, once per conversation, not ahead of time." Exclusions are stated for the optional ref parameter ("only when the task needs it") and an edge case is carved out for tailwind-upgrade without a projectId, so the agent knows exactly when this call is and is not appropriate.

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

All Xodia toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources