Torus

by sekhar14

Overview Schema Source Related Servers Discussions Admin

Python

Local

search

Read-only

Find current claims, evidence, and theses by keyword to retrieve sourced research and support investment analysis.

Instructions

Keyword search over current claims, evidence and theses.

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": "search"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	Yes
`types`	No	Object types

Output Schema

Name	Required	Description	Default
`hits`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 24, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already establish read-only and closed-world behavior. The description adds that results are limited to 'current' claims, evidence, and theses, but it does not explain matching semantics, ranking, or how currentness is defined.

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?

A single front-loaded sentence with no filler. It is efficiently sized for a short tool definition.

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?

An output schema exists, so return-value explanation is not required. However, for a generic search tool surrounded by many retrieval siblings, the description is too sparse on usage boundaries and query/limit semantics.

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 coverage is only 33%, and the description partially compensates by mapping 'claims, evidence and theses' to the types parameter. It does not clarify query syntax, matching behavior, or the limit parameter's purpose beyond the schema.

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?

States a specific verb+resource: keyword search over claims, evidence, and theses. It does not differentiate itself from sibling retrieval tools such as recall, brief, or get_entity.

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?

Provides no explicit when-to-use guidance, no exclusions, and no named alternatives. With many retrieval siblings, an agent must infer when this generic 'search' is preferable to recall, get_entity, timeline, or recent_records.

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