Strata

get_top_integrations

Retrieve ranked integrations and MCP servers for an AI ecosystem, with optional filtering by use case to find relevant tools.

Instructions

Get ranked integrations and MCP servers for an AI ecosystem. Optionally filter by use case. 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_top_integrations"
  }
}

Input Schema

Name	Required	Description	Default
`ecosystem`	Yes
`use_case`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 5, 2026

TDQS

B3.1/5.0

Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It includes a critical caveat that the data is 'intelligence, not ground truth' and recommends verification via source_urls. However, it omits other traits like rate limits or idempotency.

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?

Two sentences, 30 words, immediately stating purpose then a crucial behavioral note. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no parameter descriptions, the description does not explain what return values look like (beyond mentioning source_urls) or how to construct valid requests. Essential context is missing.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no information about valid values for 'ecosystem' or 'use_case'. No enums, examples, or formats are provided, leaving the agent to guess.

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 tool gets 'ranked integrations and MCP servers' with optional filtering by use case. It is specific about the resource and action, and distinct from siblings like 'find_mcp_servers' which likely searches unranked.

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 description does not provide guidance on when to use this tool versus alternatives such as 'find_mcp_servers' or 'search_ecosystem'. No exclusions or prerequisites are mentioned.

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

Deploy Server