Builders in Fintech

Get a weekly topic digest

get_topic_digest

Read-onlyIdempotent

The weekly digest for one topic (currently the topics with a digest, e.g. 'stablecoins', 'agentic-payments'): published news tagged with the topic or its sub-topics in one ISO week (Monday to Monday, Europe/Rome), newest first, plus the approved funding rounds linked to those stories. Amounts are never converted. Arguments: topic (required, topic slug), week (optional, 'YYYY-Www', e.g. '2026-W45'; omit for the current week). Always returns available_weeks (last 12 weeks with at least one story). Unknown topic → error listing the digest topics. Unknown arguments are rejected.

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": {
      "topic": "<topic>"
    },
    "name": "get_topic_digest"
  }
}

Input Schema

Name	Required	Description	Default
`week`	No	ISO week 'YYYY-Www' (e.g. '2026-W45'). Omit for the current week.
`topic`	Yes	Topic slug, e.g. 'stablecoins'.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses sort order (newest first), the exact week boundary (Monday to Monday, Europe/Rome), that amounts are never converted, that available_weeks is always returned, and that unknown arguments are rejected. These are exactly the behaviors an agent could not infer from structured fields.

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?

It is front-loaded with the resource and contents and packs a lot of substance per sentence. Some clauses duplicate the schema (week format, omit for current week), and the single dense sentence is heavy to parse, but there is little true waste.

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 still tells the agent what comes back (stories plus linked funding rounds, newest first, always including available_weeks) and how failures surface. For a two-parameter read tool that is fully sufficient to call it correctly.

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 100%, so the baseline is 3, but the description adds meaning the schema lacks: which topic slugs actually work, the timezone that defines the week, and the error behavior for an unknown slug. The 'YYYY-Www' format and omission-for-current-week are repeated from the schema, so it falls just short of 5.

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?

It names a specific verb and resource ('weekly digest for one topic') and immediately scopes the contents: news tagged with the topic or its sub-topics in one ISO week, plus linked funding rounds. This distinguishes it cleanly from get_daily_digest and generic content tools in the sibling list.

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?

It clarifies which topics are eligible ('the topics with a digest, e.g. ...'), says to omit week for the current week, and states that an unknown topic errors with a list of valid topics. It stops short of naming when to prefer a sibling such as get_daily_digest or search_content.

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

All Builders in Fintech tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?