Skip to main content
Glama

The labels and their fields

research_labels
Read-onlyIdempotent

The 32 served labels (genres), each with its embedding rule (never / conditional), whether it carries themes, its field prefix and structured field list. Static; read once. A never-embed label cannot be found by semantic_text. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "research_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
labelsYesThe 32 served labels

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?

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add context, and it does: the data is static and should be read once, it is free to call, and the never-embed constraint has a downstream consequence for semantic search. That last point is genuine behavioral disclosure an agent could not get from the annotations. Return format is left to 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?

Three terse clauses front-load the resource and its per-entry contents, then add two short operational notes. Nothing is redundant. The telegraphic style ('Static; read once.' and the one-word 'Free.') is efficient but slightly clipped, costing a bit of readability.

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?

An output schema exists, so return values need no prose, yet the description still sketches the entry structure. Combined with the static/free/read-once notes, an agent has enough to call this correctly and cache it. Only the absence of a routing hint to overlapping reference tools leaves a small gap.

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

Parameters4/5

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

The tool takes zero parameters, which is the baseline-4 case. The description correctly spends no words on arguments and instead characterizes the single-letter shape of the response, which is the only semantics that could matter here.

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 resource (the 32 served labels/genres) and enumerates the attributes each entry carries: embedding rule, theme flag, field prefix, structured field list. An agent knows exactly what comes back. It stops short of naming a sibling it is distinct from, so it does not reach 5.

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?

'Static; read once' gives caching/lifecycle guidance, and the note that a never-embed label cannot be found by semantic_text tells the agent why this lookup matters before searching. However, there is no explicit statement of when to call this versus related reference tools such as research_vocabulary or research_facets, so usage remains implied rather than asserted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources