Blossom Research

Browse the latest research

show_research_feed

Read-onlyIdempotent

Display a browsable latest-research feed from verified published paper IDs. First call get_latest_research, then pass only its returned paper IDs and the same query/compound filters. The server resolves those records again; never supply generated titles or summaries. An empty ID list displays the no-results state. Text-only clients still receive the published records and source links.

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": {
      "paperIds": "<paperIds>"
    },
    "name": "show_research_feed"
  }
}

Input Schema

Name	Required	Default
`query`	No
`compound`	No	all
`paperIds`	Yes

Output Schema

Name	Required	Description	Default
`type`	Yes
`limit`	Yes
`scope`	Yes
`papers`	Yes
`filters`	Yes
`dateBasis`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover safety (read-only, idempotent, non-destructive, closed-world), but the description adds genuinely new behavior: the server re-resolves records from IDs, an empty ID list renders the no-results state, and text-only clients still get records and source links. It does not mention cost, latency, or what happens if IDs no longer resolve.

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?

Four compact sentences, front-loaded with purpose then workflow, then edge cases. Every sentence carries information; slight density in the middle sentences costs it a point but 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?

An output schema exists so return values need not be described, yet the description still covers the no-results case and text-only fallback. Combined with the upstream-tool prerequisite and the parameter provenance rule, an agent has everything needed to invoke 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?

With 0% schema description coverage, the description carries the burden and does add real meaning: paperIds must be verbatim output from get_latest_research, and query/compound must match the call that produced them. It does not explain the compound enum values or the 20-item cap, leaving those to the schema.

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 and resource ('Display a browsable latest-research feed') plus the data source constraint ('from verified published paper IDs'). It distinguishes itself from get_latest_research by being the display step rather than the discovery step, though it does not mention fetch/get_paper, which also retrieve individual records.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit ordered workflow: call get_latest_research first, then pass only its returned paper IDs with the same query/compound filters. It also states a clear prohibition ('never supply generated titles or summaries'), removing the main misuse path.

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

All Blossom Research 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?