Skip to main content
Glama

Get Tag

get_tag
Read-only

Retrieve an administrative tag and its associated courses, users, and monitors using the tag ID.

Instructions

(Admin) Una tag con sus cursos, sus usuarios y sus monitores.

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

Input Schema

NameRequiredDescriptionDefault
tag_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is to add context — it does add the admin-only requirement and discloses that the response hydrates related courses, users and monitors, which is genuinely useful. It does not say what happens when tag_id does not exist (empty result vs error) or whether the nested collections are paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words, so it is appropriately sized, but it is under-specified rather than efficient: the admin qualifier is buried in parentheses and the sentence lacks a leading verb to anchor it. Nothing is front-loaded as the primary action.

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 one-parameter read-only getter with an output schema present, the description covers the essential extras — admin gating and what related entities are returned — so an agent can call it correctly without further detail. The absence of not-found behavior is a minor gap given the output schema documents the return shape.

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?

There is one required parameter, tag_id, with 0% schema description coverage, so the schema gives only a bare integer type. The description implies the tag being fetched is the one identified, but adds no format, source (where to obtain a tag_id), or error semantics — leaving the only parameter effectively undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and its returned contents ('Una tag con sus cursos, sus usuarios y sus monitores'), which goes beyond the bare name, but it never states a verb and is written as a noun phrase. It does not distinguish itself from siblings like 'list_tags' or 'tag_summary', so an agent must infer that this is the single-tag fetch.

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

Usage Guidelines2/5

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

The only usage signal is the '(Admin)' prefix, which implies a permission requirement but is not framed as guidance. There is no statement of when to use this instead of 'list_tags' (enumerate tags) or 'tag_summary' (aggregate view), nor any exclusion or precondition beyond the implicit admin scope.

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