ColdState — Deterministic Knowledge Infrastructure

coldstate_search_global

Read-onlyIdempotent

Search ColdState's global knowledge base (48.4M+ entries across 35 domains including SCIENCE, MEDICINE, TECHNOLOGY, HISTORY, etc). Returns deterministically ranked results with Ψ relevance scores and a state classification. Optionally filter by domain.

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": {
      "query": "<query>"
    },
    "name": "coldstate_search_global"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results to return
`query`	Yes	The search query
`domain`	No	Filter by knowledge domain (e.g. MEDICINE, SCIENCE, TECHNOLOGY, HISTORY, LAW, CODE). Case-insensitive.
`offset`	No	Offset for pagination

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral details beyond that: deterministic ranking, relevance scores, and state classification. No contradictions exist.

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 concise and front-loaded with the main verb and resource. It packs significant detail (scale, domains, output behavior, optional filter) into two sentences with no wasted words.

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?

Despite lacking an output schema, the description sufficiently conveys what the tool returns (ranked results with relevance scores and state classification) and covers the main use case. Combined with full schema parameter descriptions and safety-related annotations, the context is complete for an agent to invoke the tool correctly.

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 input schema provides full descriptions for all four parameters (100% coverage). The description adds minimal extra semantic value by mentioning optional domain filtering, which is already documented. It does not elaborate on limit, offset, or query formats.

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 identifies the tool as a global search over ColdState's knowledge base, with scope (48.4M+ entries, 35 domains) and unique output characteristics (Ψ relevance scores, state classification). This distinguishes it from sibling tools like coldstate_search, which likely targets a more specific subset.

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 description provides clear context: this is a global search with optional domain filtering, implying it is for cross-domain queries. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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

All ColdState — Deterministic Knowledge Infrastructure 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?