Skip to main content
Glama

Stratalize Intelligence

Get Stratalize Overview

get_stratalize_overview
Read-only

START HERE — Returns the complete Stratalize tool catalog: governed MCP tools across finance, healthcare, governance, real estate, crypto, and intelligence. Available via public MCP (no auth) or x402 micropayments on Base ($0.02 atomic · $0.10 benchmark · $0.50 synthesis · $1.00 premium · $3.00 outcome pack). Org intelligence, agent governance, and role briefs require OAuth. Call this first to discover tools by role or vertical. Free.

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_stratalize_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say readOnly/openWorld/non-destructive; the description adds substantial context the annotations do not: access is via public MCP with no auth or x402 micropayments on Base with concrete per-call price tiers, certain content requires OAuth, and the call itself is free. For an agent deciding whether it can call this at all, the auth and cost disclosure is the critical missing piece and it is supplied here.

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?

Front-loaded with the imperative 'START HERE', then purpose, then access/cost model, then the OAuth exception, then the directive — a logical order. The dense price-tier enumeration is the one stretch that reads as promotion rather than instruction, though it does carry real cost 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?

With no output schema, the description must characterize the return value, and it does ('complete Stratalize tool catalog ... discover tools by role or vertical'). Auth, pricing, and free-tier behavior are all covered. What is not covered is the shape of the response — whether it returns role groupings, tool descriptions, or callable names — which would help an agent know what to do with the result.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter-level guidance is needed or missing.

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?

States a specific verb and resource ('Returns the complete Stratalize tool catalog') and enumerates the covered verticals (finance, healthcare, governance, real estate, crypto, intelligence). It is unambiguously a discovery/catalog tool, cleanly separable from the sibling data-fetch tools like get_13f_holdings_delta or get_cap_rate_benchmark.

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?

The 'START HERE' prefix and 'Call this first to discover tools by role or vertical' give a clear, actionable trigger for invocation, which is exactly the right guidance for a catalog entry point. It stops short of a 5 because it offers no explicit when-not-to-use condition (e.g. don't re-call after discovery) and names no alternative path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources