Slacking.biz — SEC Financial Data + US Economics + Demographics + FX

get_sentiment

Get sentiment analysis from SEC filings for a company — positive/negative/neutral signals from 10-K/10-Q reports

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ticker`	Yes	Stock ticker symbol

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 28, 2026

removedInput schema / properties / filing

Removed value: -{
-  "description": "Filing type to analyze (e.g. '10-K', '10-Q')",
-  "type": "string"
-}

removedInput schema / properties / year

Removed value: -{
-  "description": "Filing year to analyze",
-  "type": "integer"
-}

First observedJul 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the output type (positive/negative/neutral) but does not mention potential requirements like API keys, rate limits, or computational cost. The behavior is partially transparent.

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?

The description is a single sentence with no wasted words. It is front-loaded with the main action and resource, making it easy to parse.

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?

Given the tool has only one parameter and no output schema, the description is mostly complete. It specifies the input and the type of analysis. A minor gap is the lack of description of the output format (e.g., scores or labels), but it is not critical for this simple tool.

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?

The schema already describes the ticker parameter as 'Stock ticker symbol' with 100% coverage. The description adds no additional meaning beyond mentioning 'a company', which aligns with the schema. 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?

The description clearly states the verb 'Get' and the resource 'sentiment analysis from SEC filings', specifying positive/negative/neutral signals from 10-K/10-Q reports. It is distinct from sibling tools like financial statements or company profile.

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?

The description implies usage for sentiment analysis from SEC filings but does not provide explicit guidance on when to use this tool versus alternatives, nor does it list when not to use it. No sibling comparisons are made.

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

All Slacking.biz — SEC Financial Data + US Economics + Demographics + FX tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.9/5.0

Disambiguation2/5

Several tool groups have overlapping purposes: fda_drug_labels vs health_drug_search, fda_recalls vs health_recalls, fx_official_rates vs treasury_fx_rates, treasury_debt vs us_debt_current, and get_gdp vs get_bea_gdp. These near-duplicates create real ambiguity for an agent deciding which tool to call.

Naming Consistency2/5

Names mix verb-led styles (get_, search_, compare_, screen_) with domain-led styles (fx_, treasury_, uk_, health_, eurostat_, datausa_). Within the same domain, similar actions use different patterns (get_gdp vs eurostat_gdp vs imf_indicator), making the set feel inconsistent and hard to predict.

Tool Count1/5

75 tools is extreme for any MCP server, especially when many tools are redundant or cover unrelated domains (weather, earthquakes, scholarly search, air quality) outside the stated SEC/economics/demographics/FX focus. This overwhelms agents and burdens context windows.

Completeness3/5

Core domains like SEC financials, major economic indicators, basic demographics, and current FX rates are well covered. However, gaps remain: no historical FX rates, no stock price/quote tool, limited demographic breakdowns, and no ability to fetch full SEC filing text. Some operations end in dead ends.

Resources

Need Help?