Tresslers Group Intelligence Matrix

search_intelligence_matrix

Executes a semantic vector similarity search across the entire ThinkForge intelligence substrate. Returns relevant snippets and strategic conviction metadata.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results to return (default 5, max 10).
`query`	Yes	Semantic research question (e.g., 'What are the geopolitical vulnerabilities in green hydrogen supply chains?').
`filter`	No	Optional SQL-like metadata filter (e.g., 'convictionScore >= 0.85').

Output Schema

TableJSON Schema

Name	Required	Description	Default
`content`	No

TDQS

A3.5/5.0

Behavior2/5

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

Annotations empty, so description must cover behavior. Only gives high-level purpose and outputs; no detail on side effects (none), error handling, or filtering behavior beyond schema. Could mention that it is read-only.

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?

Single sentence that effectively communicates the core action and result. Efficient and front-loaded.

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

Completeness3/5

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

Given the tool has 3 parameters fully described and output schema, the description is adequate but could better contextualize when to use this tool over siblings, and the meaning of 'conviction metadata'.

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 already provides full descriptions for all parameters (100% coverage). Description rephrases but adds no new semantic meaning beyond what's in schema.

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?

Clearly states it executes a semantic vector search across the entire intelligence substrate and returns relevant snippets with conviction metadata. Differentiates from siblings like ask_intelligence_rag which is more QA-focused.

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?

No explicit when-to-use or when-not-to-use compared to siblings. Implicitly for broad semantic search, but lacks guidance compared to alternatives like ask_intelligence_rag.

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

All Tresslers Group Intelligence Matrix tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool serves a distinct purpose: Q&A via RAG, updates, listing, graph traversal, full-text reading, and semantic search. No two tools overlap significantly in functionality.

Naming Consistency4/5

All names use snake_case and follow a verb_noun pattern, though some have extra qualifiers (e.g., 'ask_intelligence_rag' vs 'list_dossiers'). The pattern is predictable and readable.

Tool Count5/5

With 6 tools, the server is well-scoped for an intelligence retrieval system. Each tool contributes a necessary operation without superfluous clutter.

Completeness4/5

The tool surface covers core operations for a read-only intelligence repository: listing, searching, reading, asking questions, and tracking updates. Minor metadata features are missing but not critical.

Resources

Need Help?