Skip to main content
Glama

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

text_sentiment

Read-onlyIdempotent

utilpeek: Analyze the sentiment of an English text. For your own labels use classify_zero_shot; for counts use text_stats. Returns VADER sentiment of an English text: compound (-1 to 1), positive / neutral / negative shares and a label (positive at 0.05 or more, negative at -0.05 or less), optionally per sentence. A lexicon heuristic: it misses sarcasm and domain jargon. Typically under 1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/sentiment-analysis-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": "text_sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text (at most 200,000 characters).
per_sentenceNoAlso score each sentence (default false: whole text only).

Output Schema

NameRequiredDescriptionDefault
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
labelNo
methodNo
sourceNo
neutralNo
compoundNo
languageNo
negativeNo
positiveNo
sentencesNo
input_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / per_sentence / title
      Removed value: -"Per Sentence"
    • removedInput schema / properties / text / title
      Removed value: -"Text"
    • removedInput schema / title
      Removed value: -"text_sentimentArguments"
  2. Changed2 schema fields changed
    • addedInput schema / properties / per_sentence / description
      Added value: +"Also score each sentence (default false: whole text only)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "compound": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "input_truncated": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "label": {
      +      "enum": [
      +        "positive",
      +        "neutral",
      +        "negative",
      +        null
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "language": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "method": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "negative": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "neutral": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "positive": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "sentences": {
      +      "type": [
      +        "integer",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the VADER heuristic, its known weakness with sarcasm and domain jargon, typical latency under 1 s, price and free-tier limits, and that submitted text is not stored. These are decision-relevant behavioral traits that the readOnly/idempotent annotations do not cover.

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 alternatives are front-loaded, and each sentence adds useful information. It is slightly dense with pricing, free-tier, privacy, and documentation details, but none are irrelevant to deciding whether to call the tool.

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 output schema exists, the description need not explain return values, yet it still clarifies the VADER output fields and thresholds. It also covers accuracy limits, latency, cost, and privacy, leaving nothing material an agent needs in order to call it correctly.

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 coverage is 100%, so both parameters are already fully documented in the input schema. The description restates that scoring can be per sentence but adds no new meaning beyond the schema's own parameter descriptions, so baseline 3 is appropriate.

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?

States a specific verb and resource: 'Analyze the sentiment of an English text.' It also explicitly distinguishes itself from siblings by saying to use classify_zero_shot for custom labels and text_stats for counts.

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

Usage Guidelines5/5

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

Names two alternatives and the exact condition that selects each: custom labels go to classify_zero_shot, counts go to text_stats. This is explicit when-to-use guidance with no inference required.

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.