Skip to main content
Glama

Embeddings, Rerank & Speech-to-Text (Tanod)

extract_entities

Read-onlyIdempotent

mlpeek: Extract named entities: people, organisations, places, dates, money, ... For fields of your own schema use extract_json_with_schema. Returns named entities in English text with spaCy en_core_web_sm 3.8.0 (MIT): text, label (the 18 OntoNotes types: PERSON, ORG, GPE, LOC, DATE, MONEY, ...) and code-point offsets (end exclusive), plus counts per label; at most 2,000 entities (then entities_truncated). A statistical model: it can miss or mislabel entities. English only. Runs an open model pinned by hash on Tanod's own CPU (no LLM, no third-party API); an unavailable model is a 503 (not charged). Typically under 0.1 s for 2,000 characters, under 0.5 s at 20,000. Price: USD 0.001. Free: 5 mlpeek calls per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/named-entity-recognition-zero-shot-classification-api.html

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

Input Schema

NameRequiredDescriptionDefault
textYesEnglish text, at most 20,000 characters.
labelsNoOnly these entity types (default: all 18 OntoNotes types).

Output Schema

NameRequiredDescriptionDefault
noteNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
modelNo
chunksNo
countsNo
entitiesNo
chars_analyzedNo
entities_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / labels / default
      Removed value: -null
    • removedInput schema / properties / labels / title
      Removed value: -"Labels"
    • removedInput schema / properties / text / title
      Removed value: -"Text"
    • removedInput schema / title
      Removed value: -"extract_entitiesArguments"
    • removedOutput schema / properties / counts / additionalProperties
      Removed value: -{
      -  "type": [
      -    "integer",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / entities / items
      Removed value: -{
      -  "properties": {
      -    "end": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "label": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "start": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "text": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / model / properties
      Removed value: -{
      -  "alias": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "id": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "revision": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "source": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "chars_analyzed": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "chunks": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "counts": {
      +      "additionalProperties": {
      +        "type": [
      +          "integer",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "entities": {
      +      "items": {
      +        "properties": {
      +          "end": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "label": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "start": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "text": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": [
      +          "object",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "entities_truncated": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "model": {
      +      "properties": {
      +        "alias": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "id": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "license": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "revision": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "source": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds substantial context beyond those annotations: the pinned spaCy model, statistical miss/mislabel caveat, 2,000-entity truncation flag, English-only constraint, 503 behavior, latency, price, free tier, and privacy handling. That is unusually complete behavioral disclosure.

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?

The purpose and sibling routing are front-loaded, and the remaining sentences are dense with operational details rather than filler. The description is long and mostly a single block, but nearly every sentence earns its place for a paid external API. Minor structural improvement could come from separating output, limits, and pricing details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool is a paid, model-backed extractor with an output schema, the description covers the essential context: output shape, entity cap, model limitations, language restriction, error behavior, latency, cost, rate limit, and privacy. Nothing an agent needs in order to select or invoke it correctly appears to be missing.

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 both the text and labels parameters are already documented structurally. The description reinforces the 18 OntoNotes entity types and default-all behavior, but it does not add parameter syntax or constraints beyond what the schema provides. Baseline 3 is appropriate when the schema carries parameter semantics.

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: extracting named entities such as people, organisations, places, dates, and money. It also distinguishes itself from the sibling extract_json_with_schema by saying that tool is for fields of your own schema. An agent can identify the tool's purpose without opening the schema.

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 explicitly routes custom-schema extraction to extract_json_with_schema, which gives clear alternative guidance. It also implies limits via 'English only' and the statistical-model caveat, but it does not enumerate every case where another extractor might be preferable. The guidance is strong but not exhaustive.

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.