Skip to main content
Glama

Blog Search

tt_blog_search
Read-onlyIdempotent

Search or browse PUBLISHED posts on the Tradetron blog (tradetron.tech/blog): guides on options strategies, backtesting, algo trading basics, risk management, Tradetron features. query = full-text search; empty = latest posts (paged, optionally by category slug; the first unfiltered page also lists the categories). Returns title, excerpt, url, slug. Use it to answer "is there a guide on X" and to cite an article. No sign-in needed.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
queryNo
categoryNo
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond them: the published-only scope, the "No sign-in needed" auth note, and the pagination/category behavior including that the first unfiltered page lists categories. It does not state ordering, total counts, or what an empty result looks like.

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-loads the core action and scope, then the topic list, then parameter behavior, then return fields and the auth note. The parenthetical about category and the first page listing categories is slightly dense but every sentence carries information; nothing is filler.

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?

For a 4-param, no-output-schema read tool, the description covers scope, auth requirements, empty-query fallback, pagination awareness, category filtering, and the returned fields (title, excerpt, url, slug). The main remaining gap is paging semantics for `page`/`page_size`, which both the schema and description leave undefined.

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 description coverage is 0%, so the description must carry all parameter meaning, and it does so only partially. It explains `query` (full-text; empty = latest) and `category` (a slug, optional filter), but `page` and `page_size` are only gestured at with "paged" and no semantics, bounds, or defaults are given for them.

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 pair ("Search or browse PUBLISHED posts on the Tradetron blog") and enumerates the content domain (options strategies, backtesting, algo basics, risk management, Tradetron features). The uppercase PUBLISHED scopes it to non-draft content, implicitly contrasting with tt_blog_submit_draft, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

Gives concrete usage contexts: answering "is there a guide on X" and citing an article, plus the operational rule that an empty query returns latest posts. It stops short of explicit when-not or naming tt_blog_read_post as the follow-up for full article content, which an agent must infer from the returned fields.

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