Skip to main content
Glama

job_ner_gliner

Extract named entities of the types you name (GLiNER, zero-shot)

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": {
      "text": "<text>"
    },
    "name": "job_ner_gliner"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesthe text
labelsNoentity types to find (default: person, organization, location, date)
thresholdNoscore threshold (default 0.5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose a meaningful behavioral trait beyond the schema — that extraction is zero-shot, i.e. no fixed entity list and no model training required — but says nothing about the return shape (entity spans, labels, scores?), whether a local model is invoked or a rate-limited API, or the behavior when the threshold filters everything out.

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?

A single sentence, front-loaded with the action and resource, with the distinguishing qualifier in parentheses. Nothing is redundant or padded given the small surface area.

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?

The tool is simple (3 params, one required), the schema is fully documented, and there is no output schema. Still, with no annotations and no output schema, the description should describe what comes back — entity spans, labels, confidence values — and it does not, leaving the response format a complete unknown.

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 100%, so all three parameters and their defaults (default label set, default 0.5 threshold) are already documented. The phrase "of the types you name" loosely reinforces the `labels` parameter, but the description adds no threshold-tuning advice, label formatting conventions, or interaction between labels and threshold.

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?

The description names a specific verb and resource ("Extract named entities") and adds the distinguishing qualifier "GLiNER, zero-shot" plus "of the types you name", which tells the agent this is configurable-label extraction rather than a fixed-classifier NER. None of the listed siblings (OCR, transcription, rendering, YouTube jobs) do entity extraction, so the tool is easy to tell apart.

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?

There is no when-to-use guidance: no indication that this is for text already in hand, no pointer to preprocessing siblings (e.g. OCR/transcript tools) when the input is an image or audio, and no stated preconditions. The agent must infer the usage context entirely from the tool name.

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