Skip to main content
Glama

Fork a hub card

fork_rubric

Copy a published rubric card into this server as a new rubric for evaluate to use, preserving the original and recording its source and licence.

Instructions

Copy a published card into this server's rubrics (a new rubric id; the card is not changed) so evaluate can use it. The rubric's metadata records where it came from and its licence.

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

Input Schema

NameRequiredDescriptionDefault
hubNo
refYes
nameNoname for the copy (default: the card's)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses that a new rubric id is created, that the source card is not modified, and that metadata records provenance and licence. It omits auth requirements, idempotency/duplicate-fork behavior, and whether the response returns the new id.

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?

Two tight sentences, front-loaded with the core action and the non-destructiveness guarantee in a parenthetical. No filler or redundant restatement of the name.

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?

A mutating tool with no annotations and no output schema needs more: the response shape (does it return the new rubric id?), the meaning of `hub`/`ref`, and duplicate-fork behavior are all missing. The description does cover the essential purpose, source immutability, and provenance recording, so it is adequate but incomplete.

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 33% — just `name` is documented — and the description never explains `ref` (what a card reference looks like) or `hub` (which hub server to fork from). The phrase 'where it came from' hints at provenance metadata but adds no usable meaning to the two undocumented parameters.

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?

States a specific verb and resource: copy a published card into this server's rubrics, producing a new rubric id without changing the source card. It also names the downstream consumer (`evaluate`), which separates it from `create_rubric` and from read-only siblings like `hub_get`.

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 by 'so `evaluate` can use it' — fork when you want to evaluate a hub card locally. There is no explicit when-not guidance, no mention of when to prefer `hub_get`/`hub_search` first, and no note on what happens if the card was already forked.

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