Skip to main content
Glama
Sign In
Strata

Strata

by PThrower
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_latest_news

Retrieve news and updates for any AI ecosystem. Items include content age and freshness indicators; verify critical decisions against source URLs.

Instructions

Get the latest news and updates for an AI ecosystem. Pro tier receives real-time results. Free tier receives items older than 24 hours. Each item includes content_age_hours and data_freshness — check these before acting on time-sensitive information. Strata provides intelligence, not ground truth. Always verify critical decisions against the source_urls returned with each item.

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": {
      "ecosystem": "<ecosystem>"
    },
    "name": "get_latest_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
ecosystemYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Discloses tier-dependent latency, item fields (content_age_hours, data_freshness), and the nature of data as intelligence rather than ground truth. This is comprehensive for a read-only tool with no annotations.

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?

Three well-structured sentences, front-loaded with purpose, followed by important behavioral details. No redundant information.

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?

Covers purpose, tier behavior, item fields, and verification guidance. Lacks explicit mention of the limit parameter and response structure, but the tool is simple and the description is sufficient for basic use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has two parameters (ecosystem, limit) with 0% description coverage. Description implies ecosystem through the tool's purpose but does not mention the limit parameter at all, leaving its role undocumented.

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?

Description clearly states 'Get the latest news and updates for an AI ecosystem', specifying a concrete action and resource. It differentiates from siblings which focus on servers, practices, integrations, and ecosystem listing/search.

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?

Provides tier-based latency guidance (Pro tier real-time, Free tier 24h delay) and advises checking content_age_hours for time-sensitive information. Also includes a caution about verifying critical decisions via source_urls. Does not explicitly compare to alternative tools, but context is clear.

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

Deploy Server

Other Tools