GeoQuant Orb

palantir

get_palantir

Read-only

Okhotnik Palantir feed (curated items pushed by Okhotnik + build-time snapshot) merged with fresh news-live headlines tagged palantir / east_flank / compliance (source "news-live"), newest first, with verification status and freshness (as_of, newest_item_age_sec). Use display_title / title_en (English; null when only a non-English original exists). Optional topic filter: palantir, ai_military (alias ai-military, killchain), east_flank (alias east-flank), compliance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_palantir"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	No	optional filter: palantir, ai_military (alias ai-military, killchain), east_flank (alias east-flank), compliance

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / topic

Added value: +{
+  "description": "optional filter: palantir, ai_military (alias ai-military, killchain), east_flank (alias east-flank), compliance",
+  "enum": [
+    "palantir",
+    "ai_military",
+    "ai-military",
+    "killchain",
+    "east_flank",
+    "east-flank",
+    "compliance"
+  ],
+  "type": "string"
+}

First observedOct 22, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already mark this as read-only and open-world, and the description adds substantial behavioral detail beyond that: the feed merges curated pushed items with a build-time snapshot and fresh headlines, results are newest first, and it discloses freshness fields (as_of, newest_item_age_sec) plus English-title fallback behavior. No annotation contradiction.

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 description is dense and front-loaded, with no wasted sentences. The first sentence is long and parenthetical-heavy, but each clause contributes useful scoping or return-field information.

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?

With no output schema, the description carries the burden of explaining return content, and it does so well by naming the verification, freshness, and title fields. It also explains the merge behavior and ordering, leaving little ambiguity for an agent to call and interpret the feed.

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%, so the single optional topic parameter is already fully documented. The description repeats the same enum values and aliases without adding new syntax or format guidance, making 3 the appropriate baseline.

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?

The description states a specific resource and scope: an Okhotnik Palantir feed merged with fresh news-live headlines tagged palantir/east_flank/compliance. It is clearly distinct from a general news feed, but it does not explicitly name a sibling tool or contrast itself with get_news_live or get_news_snapshot.

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?

Usage is implied by the topic filter and the Palantir-specific feed content, but the description never states when to choose this tool over get_news_live, get_news_snapshot, or get_brief, nor does it give any exclusion conditions.

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

All GeoQuant Orb 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.

Resources

Need Help?