Skip to main content
Glama

codex_skills

Read-onlyIdempotent

Lists available native skills for a project and lets you select enabled skills by name for start or send tasks without changing global skill configuration.

Instructions

List native skills available for this project. Select enabled skills by name in start/send; no global skill configuration changes.

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

Input Schema

NameRequiredDescriptionDefault
task_idYesTask id
force_reloadNo

Output Schema

NameRequiredDescriptionDefault
okYes
result_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description's contribution is clarifying that listing has no side effects on global skill configuration, which is useful context. It says nothing about caching or what force_reload does despite force_reload existing, and nothing about the shape of the listing beyond the output schema.

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 short sentences with the primary purpose front-loaded and no filler. The second sentence packs two distinct facts (how to enable skills, no global config mutation) but remains compact.

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?

An output schema exists so return values need no explanation, and annotations cover safety. However, for a two-parameter tool with half its schema undocumented, the definition leaves force_reload's purpose and effect unexplained, which is a meaningful gap for correct invocation.

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

Parameters2/5

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

Schema coverage is only 50%: task_id has a bare 'Task id' note and force_reload has no description at all. The description adds no parameter meaning whatsoever — it never mentions task_id scoping or when a forced reload would be needed — so the undocumented force_reload parameter is left entirely ambiguous.

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?

States a specific verb and resource ('List native skills') plus a scope ('available for this project'), which is enough to distinguish it from project/session tools like codex_projects or codex_sessions. It does not explicitly name a contrasting sibling, so it stops short of a 5.

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

Usage Guidelines4/5

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

The description tells the agent what to do with the result — 'Select enabled skills by name in start/send' — which is genuine downstream routing guidance. 'No global skill configuration changes' also implicitly excludes configuration-editing use cases, though no alternative tool is named for that.

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