Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Fork Codex part

fork_part

Copy a built-in or community part into your own Codex to customize it for your schematic without altering the shared original.

Instructions

Copy a built-in or community part into your own Codex so you can edit 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": {
      "part_id": "<part_id>"
    },
    "name": "fork_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
part_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is supplied. The description adds genuine context beyond that: the operation creates a private, editable copy rather than altering the original built-in/community part. It does not say what happens on a repeat fork of the same part (overwrite, duplicate, error) or what identifier the new copy receives.

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?

One sentence, front-loaded with the action, with zero redundant wording. Nothing is wasted and the destination/benefit clause earns its place.

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?

For a single-parameter, non-destructive mutation with no output schema and annotations already covering the safety profile, the description is close to sufficient. It leaves out what the tool returns (new part ID?) and how it relates to save_part, which an agent needs to chain the workflow correctly.

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 description coverage is 0% for the single part_id parameter, so the description carries the full burden and does not meet it. It mentions that parts may be 'built-in or community' but never explains how part_id resolves across those two sources or what form the identifier takes.

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 description names a specific verb+resource pair ('Copy a ... part') and scopes the operation precisely: source is a built-in or community part, destination is your own Codex. An agent can distinguish it from save_part, which edits something already owned, though the description does not name that sibling explicitly.

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 through the phrase 'so you can edit it' — you fork when you need to modify a part you don't own. There is no explicit when-not guidance, no mention of the follow-up step (editing then saving via save_part), and no prerequisites such as account or workspace constraints.

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