Skip to main content
Glama

Create Tag

create_tag

Creates an Orbits assessment tag for grouping drafts, tests, or question bundles; check existing tags first to avoid duplicates.

Instructions

(Admin) Crea una tag (p. ej. «Solución Algorítmica 2027-1 - Sección A»). Revisa list_tags antes para no duplicar.

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": "create_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive mutation, so the safety profile is covered. The description adds a genuinely useful behavioral fact beyond the annotations — that the operation requires admin rights ("(Admin)") — but says nothing about duplicate-name behavior or idempotency.

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 short sentences, front-loaded with the action and an example, followed by the duplicate-avoidance instruction. No filler or redundant restatement of the title.

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?

For a simple two-parameter create tool with annotations covering the safety profile and an output schema covering return values, the definition covers the essentials: purpose, naming example, admin requirement, and a duplicate pre-check. The only gap is the undocumented optional `description` field.

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 0%, so the schema provides no meaning for the two parameters. The description partially compensates by illustrating the format of the required `name` value, but the optional `description` parameter is never mentioned or explained.

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 gives a specific verb and resource ("Crea una tag") plus a concrete example value that shows the expected naming convention. It is clearly distinct from delete_tag/get_tag, though it does not explicitly contrast with the other creation siblings like create_course.

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?

It states an explicit prerequisite workflow: check list_tags first to avoid creating duplicates. It gives no explicit when-not guidance or error-handling advice if the tag already exists, so it falls short of a full 5.

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