Skip to main content
Glama

classifier.dev

by dev.classifier
OverviewDiscussionsAdmin

Classify several dimensions per text

classify_dimensions

Classify each text by several named dimensions, such as team, urgency and kind, in one request. Returns a label, confidence, scores and model for each field. At most 1,000 item × dimension decisions; every field counts toward the quota. Use per-dimension instructions to define ambiguous categories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoScrape one public URL instead of inputs/items. Requires funded workspace access. Context.dev costs $0.0022 per billed attempt plus classification; long articles need Fast. Errors disclose retained charges. No automatic scrape retries.
tierNofast (default) or smart, which re-asks answers under 0.7 confidence of a reasoning model (slower, single-label only). Independent of the Laya processing lane.
itemsNo1 to 1,000 texts to classify. Results come back in the same order.
modelNo
includeNoWith url: return article.markdown and/or article.html at no extra scrape cost. Omit for compact output.
dimensionsYesNamed dimensions. Each is a label array or {labels, instructions}. At most 1,000 item × dimension decisions; definitions at most 16,000 characters combined.
processingNoOptional. Implies Laya if model is omitted; has no effect with explicit Jev. Omit for automatic fast/bulk selection based on item × dimension decisions.
share_dataNoSynchronous classification request text, labels, instructions and model results are retained for model training and operator review in private Cloudflare storage by default. Shared requests receive double per-minute and daily classification quotas. Set share_data: false or X-Classifier-Share-Data: false to opt out and use standard limits. Share only data you have permission to contribute; do not include confidential or personal information. Redaction is best effort. Billing, spending caps and input-size limits still apply.
instructionsNoOptional extra criteria, e.g. "judge only the service, ignore the food".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / share_data / default
      Previous value: -falseNew value: +true
    • changedInput schema / properties / share_data / description
      Previous value: -"Opt in to retaining this request's text, labels, instructions and model results for model training and operator review in private Cloudflare storage. Doubles per-minute and daily classification quotas. Off by default. Share only data you have permission to contribute; do not include confidential or personal information. Redaction is best effort. Billing, spending caps and input-size limits still apply."New value: +"Synchronous classification request text, labels, instructions and model results are retained for model training and operator review in private Cloudflare storage by default. Shared requests receive double per-minute and daily classification quotas. Set share_data: false or X-Classifier-Share-Data: false to opt out and use standard limits. Share only data you have permission to contribute; do not include confidential or personal information. Redaction is best effort. Billing, spending caps and input-size limits still apply."
  2. Changed1 schema field changed
    • addedInput schema / properties / share_data
      Added value: +{
+  "default": false,
+  "description": "Opt in to retaining this request's text, labels, instructions and model results for model training and operator review in private Cloudflare storage. Doubles per-minute and daily classification quotas. Off by default. Share only data you have permission to contribute; do not include confidential or personal information. Redaction is best effort. Billing, spending caps and input-size limits still apply.",
+  "type": "boolean"
+}
  3. Changed4 schema fields changed
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "not": {
+      "required": [
+        "url"
+      ]
+    },
+    "required": [
+      "items"
+    ]
+  },
+  {
+    "not": {
+      "required": [
+        "items"
+      ]
+    },
+    "required": [
+      "url"
+    ]
+  }
+]
    • addedInput schema / properties / include
      Added value: +{
+  "description": "With url: return article.markdown and/or article.html at no extra scrape cost. Omit for compact output.",
+  "items": {
+    "enum": [
+      "markdown",
+      "html"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / url
      Added value: +{
+  "description": "Scrape one public URL instead of inputs/items. Requires funded workspace access. Context.dev costs $0.0022 per billed attempt plus classification; long articles need Fast. Errors disclose retained charges. No automatic scrape retries.",
+  "maxLength": 8192,
+  "pattern": "^https?://",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "items",
-  "dimensions"
-]New value: +[
+  "dimensions"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "jev",
-  "laya",
-  "kev"
-]New value: +[
+  "jev",
+  "laya",
+  "kev",
+  "chunklaya"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "jev",
-  "laya"
-]New value: +[
+  "jev",
+  "laya",
+  "kev"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / processing / description
      Previous value: -"Use bulk for multiple Laya decisions."New value: +"Optional. Implies Laya if model is omitted; has no effect with explicit Jev. Omit for automatic fast/bulk selection based on item × dimension decisions."
  7. Changed3 schema fields changed
    • addedInput schema / properties / model
      Added value: +{
+  "enum": [
+    "jev",
+    "laya"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / processing
      Added value: +{
+  "description": "Use bulk for multiple Laya decisions.",
+  "enum": [
+    "fast",
+    "bulk"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / tier / description
      Previous value: -"fast (default, ~1s per 1,000) or smart, which re-asks answers under 0.7 confidence of a reasoning model (slower, single-label only)."New value: +"fast (default) or smart, which re-asks answers under 0.7 confidence of a reasoning model (slower, single-label only). Independent of the Laya processing lane."
  8. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations (readOnly=false, openWorld=true, idempotent=false, destructive=false) cover the safety profile, and the description adds real value beyond them: the per-field return shape (label, confidence, scores, model) and the hard quota that every field counts toward. It does not cover tier cost/retry behavior, but the schema's own parameter descriptions carry those details.

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 front-loaded sentences: purpose, return shape, then quota and the instructions tip. No filler, though the quota constraint is somewhat wedged between the return description and the guidance.

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?

No output schema exists, so the description legitimately compensates by naming the returned fields (label, confidence, scores, model) and the batch quota. With 89% param coverage and annotations present, the remaining gap (model/tier tradeoffs) is handled by the schema itself.

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 89%, so the schema already documents url, tier, items, include, share_data, etc. The description only reinforces the dimensions concept ('use per-dimension instructions'), adding marginal meaning beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb (classify) and resource (each text across several named dimensions) and gives concrete examples (team, urgency, kind). It implies the multi-dimension batching that separates it from single-label siblings, though it never explicitly names classify_multi_label or classify_texts.

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?

'Use per-dimension instructions to define ambiguous categories' gives one concrete usage tip, and the quota rule ('at most 1,000 item × dimension decisions') constrains sizing. However there is no explicit when-to-use guidance or the conditions under which a sibling such as classify_multi_label should be preferred.

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

All classifier.dev toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources