Skip to main content
Glama

Blog Read Post

tt_blog_read_post
Read-onlyIdempotent

Read one PUBLISHED Tradetron blog post in full, as markdown (with its title, author, dates and canonical URL). slug from tt_blog_search or the post URL. Cite the URL when you quote it; blog content is education, not investment advice. No sign-in needed.

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": {
      "slug": "<slug>"
    },
    "name": "tt_blog_read_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding the output shape, the published-only restriction, and the 'no sign-in needed' auth note. It stops short of describing pagination or behavior on a missing/unpublished slug, which are the remaining unknowns.

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?

Three short sentences, front-loaded with the action and scope, then parameter sourcing, then usage caveats. Every clause carries information; nothing is redundant with the title.

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?

For a one-parameter read tool with no output schema, the description supplies the return format, the auth stance, and the content-type caveat ('education, not investment advice'). Nothing an agent needs to call and interpret this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the single parameter, and it does: it defines where the slug comes from (tt_blog_search output or the post URL). It adds real provenance meaning beyond the bare 'slug: string' schema, though it doesn't state format constraints such as casing or trailing segments of a URL.

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?

States a specific verb and resource ('Read one PUBLISHED Tradetron blog post in full'), plus the exact return format (markdown with title, author, dates, canonical URL). The 'PUBLISHED' qualifier and the pointer to tt_blog_search for obtaining a slug cleanly separate it from the search sibling.

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?

Implies a workflow by naming tt_blog_search as the source of the slug and accepting a post URL as an alternative, and the 'PUBLISHED' qualifier tells the agent drafts aren't readable here. There is no explicit 'use this when…' clause, but the context is clear enough to select correctly.

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