Skip to main content
Glama
Sign In
MIKO MCP Server

MIKO MCP Server

by Miko-Protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

MIKO Trending Narratives

miko.narratives_trending
Read-only

Retrieve top narratives ranked by importance and uniqueness within a selected time window (1 to 7 days).

Instructions

Get the top narratives in the requested window, ranked by importance and uniqueness.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "miko.narratives_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNoAggregation window (1d..7d)1d

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations (readOnlyHint, openWorldHint) already indicate safety and non-exhaustiveness. The description adds that results are 'ranked by importance and uniqueness', which informs agents of the sorting behavior beyond what annotations provide. No contradictions.

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?

The description is a single concise sentence that front-loads the action and key details. No unnecessary words.

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 simple read-only list tool with one optional parameter and safety annotations, the description is largely adequate. It does not describe the output structure, but the tool's simplicity and lack of output schema make this a minor gap.

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 single parameter 'window' is fully described in the schema (enum, default, description). The tool description adds no additional semantic value beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the tool retrieves 'top narratives', specifies the filtering by 'requested window', and notes they are 'ranked by importance and uniqueness', providing a distinct purpose from sibling tools like miko.narrative or miko.factcheck.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives such as miko.narrative or miko.factcheck, nor does it mention any prerequisites or exclusions. Usage context is only implied.

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

Deploy Server

Other Tools