Skip to main content
Glama
Sign In
tero-mcp-lite

tero-mcp-lite

by Aphelion-Development
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

text_search

Search a Tero corpus by free text and receive ranked results from id, title, and summary fields.

Instructions

Ranked free-text search over id/title/summary.

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": {
      "value": "<value>",
      "token": "<token>"
    },
    "name": "text_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesbearer token (from TERO_TOKENS)
valueYesthe query text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It only states ranking and search scope but does not disclose authentication requirements, return format, pagination, or side effects. 'Ranked' adds minimal behavioral context.

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 a single, well-structured sentence that is front-loaded and free of irrelevant detail, making it highly concise.

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?

Without an output schema or annotations, the description should explain return values and usage context. It only states scope and ranking, leaving gaps about response structure, error handling, and token usage. This is incomplete for a search tool.

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 100%, so the baseline is 3. The description adds no additional parameter semantics beyond the schema's own descriptions for token and value.

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 performs a ranked free-text search over id/title/summary, using a specific verb and resource scope. It distinguishes itself from sibling query_by_* tools which likely use structured queries.

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?

The description implies usage for free-text search over specific fields but does not explicitly state when to prefer this tool over alternatives like query_by_id or query_by_status, nor any exclusions.

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

Deploy Server

Other Tools