Gemral Edge

Language Drift & Semantic Retreat

get_language_drift

Measure corporate language retreat and semantic hedging over sequential quarters. Identifies silent guidance dilution, hedging markers, and early warning alerts before formal deadline slips are filed.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_language_drift"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	No	Optional topic/taxonomy filter, e.g. OPS-RAMP or PROD-LAUNCH
`ticker`	Yes	Stock ticker symbol, e.g. TSLA

Output Schema

Name	Required	Description
`notice`	No	Free-tier upgrade notice; only when results are masked/delayed.
`results`	Yes	Tool result payload (read-only evidence). Shape varies by tool; scoring weights are never exposed.
`history_limit`	No	Present when the license limits history depth: earliest_allowed date, history_days and how many older items were removed.
`deprecated_fields`	No	Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / deprecated_fields

Added value: +{
+  "description": "Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 23, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations declare openWorldHint=false and destructiveHint=false, and the description adds that the analysis is sequential-quarter based and produces early-warning alerts — useful context beyond the structured fields. But readOnlyHint=false is left unexplained for what reads as a pure analysis tool, and nothing is said about cost, latency, or whether analysis is stored. No contradiction, but the gap around the non-read-only hint is notable.

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?

Two tight sentences with the core measurement statement front-loaded and the detection/alerts scope second. No filler, though the second sentence leans on undefined buzzwords rather than concrete detail.

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?

An output schema exists, so return values needn't be explained, and both parameters are documented in the schema. Still missing are the analysis window (how many quarters are compared), the granularity of the drift measurement, and any resolution of the readOnlyHint=false ambiguity for a tool that appears purely analytical.

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% with two well-documented parameters (ticker and optional topic/taxonomy filter), so the schema carries the semantics. The description adds nothing about the topic taxonomy, quarter windows, or what happens with an unrestrictive topic — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description supplies a verb+resource ('Measure corporate language retreat and semantic hedging over sequential quarters') and lists the phenomena detected (hedging markers, early warning alerts), so the general intent is graspable. However, 'language retreat' and 'silent guidance dilution' are undefined metaphors, and nothing distinguishes this from sibling analysis tools like get_guidance_accuracy, get_management_credibility, or get_open_promises.

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?

The only usage cue is the temporal hint 'before formal deadline slips are filed,' which implies an early-warning use case but never states when to choose this tool over the numerous adjacent signal/guidance siblings. No prerequisites, no exclusions, no alternative named.

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

All Gemral Edge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.