Skip to main content
Glama

SMIFS Limited

Read a SMIFS research post

get_research_post
Read-onlyIdempotent

Full text of one SMIFS research or market-commentary post, by slug or smifs.com URL (from search_research): title, publish date, author, reading time, summary and body as plain text (long posts are truncated and flagged). Research is general information, not personalised investment advice; cite the post URL and date.

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

Input Schema

NameRequiredDescriptionDefault
slugYesPost slug, or its URL such as https://smifs.com/research-insights/blog/<slug>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description still adds real value beyond them: long posts are truncated and flagged, and output includes a citation/date disclaimer about it not being personalised advice.

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?

Two sentences, front-loaded with the payload and its inputs, followed by a short disclaimer. Dense but every clause carries information; nothing is padding.

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?

With no output schema, the description compensates by listing the returned fields and the truncation caveat. For a one-parameter read tool with full annotation coverage, nothing an agent needs to call it correctly is missing.

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% and the single slug parameter is already documented with length limits and the URL form. The description only restates the 'slug or smifs.com URL' duality, adding no new syntax or fallback guidance, so the schema does the heavy lifting.

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 ('Full text of one SMIFS research or market-commentary post') and enumerates the returned fields, so the agent knows exactly what it gets. The 'from search_research' parenthetical and the 'one post' scope separate it cleanly 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?

The '(from search_research)' note establishes the intended workflow: search first, then fetch a single post by slug or URL. It gives clear positive guidance but does not state exclusions or what to do if the slug is unknown/invalid.

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