Skip to main content
Glama

FinPortal.mk Financial Intelligence

Краток преглед на сторија

get_blog_story_summary
Read-onlyIdempotent

Retrieve the public summary for a published FinPortal story by slug. Returns a short displayed excerpt and source link only; do not use it to retrieve third-party full text.

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_blog_story_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context by specifying that the response is limited to a short displayed excerpt and source link, and by warning against expecting full text.

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?

Two tightly written sentences, with the core purpose front-loaded and the key limitation stated immediately afterward. No filler or redundant restatement of the title.

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 low-complexity, single-parameter read tool with annotations and no output schema, the description covers the essential purpose, return scope, and main exclusion. It could still say how to obtain a valid slug, but overall it is sufficient for correct invocation.

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?

The sole parameter is 'slug' with 0% schema description coverage. The description adds some meaning by indicating it identifies a published FinPortal story, but it does not explain slug format, where to obtain it, or what happens for invalid/unpublished slugs.

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: retrieve the public summary for a published FinPortal story by slug. It also clarifies the output scope (short excerpt and source link), which distinguishes it from full-text or editorial article retrieval.

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?

Explicitly says not to use this tool for third-party full text, giving a clear usage boundary. However, it does not name the preferred alternative sibling (such as get_editorial_article or search_finportal) for obtaining full text or finding slugs.

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