Minutes of AI

Search stories

search_stories

Read-only

Full-text search over published headlines and ledes.

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": {
      "query": "<query>"
    },
    "name": "search_stories"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes
`license`	No
`attribution`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 9, 2026

addedOutput schema / properties / data / items / properties / affects

Added value: +{
+  "description": "sectors and functions the event affects",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / data / items / properties / aiDisclosure / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / data / items / properties / aiGenerated / description

Previous value: -"true: the text is AI-generated from the listed sources (EU AI Act Art. 50(4) label)"New value: +"true: the text is AI-generated from the listed sources (EU AI Act Art. 50(4) label); false only for wire_link items"

changedOutput schema / properties / data / items / properties / disclosure / enum

Previous value: -[
-  "ai",
-  "reviewed"
-]New value: +[
+  "ai",
+  "reviewed",
+  "link"
+]

addedOutput schema / properties / data / items / properties / format / description

Added value: +"one of breaking, model_drop, the_number, money, explainer, rumor, for_the_minutes, standard, wire_link; wire_link = an outlet's headline and a link to its report, no text by Minutes of AI"

addedOutput schema / properties / data / items / properties / lane

Added value: +{
+  "description": "builders: SDK and library releases, checkpoints, repository signals",
+  "enum": [
+    "business",
+    "builders",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / data / items / properties / wireLink

Added value: +{
+  "description": "wire_link only: {outlet, url, originalHeadline, publishedAt, supersededBy}",
+  "type": "object"
+}

Changed6 schema fields changedOct 7, 2026

addedOutput schema / properties / data / items / properties / aiDisclosure
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / data / items / properties / aiGenerated

Added value: +{
+  "description": "true: the text is AI-generated from the listed sources (EU AI Act Art. 50(4) label)",
+  "type": "boolean"
+}

addedOutput schema / properties / data / items / properties / disclosure

Added value: +{
+  "enum": [
+    "ai",
+    "reviewed"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / data / items / properties / outletCount / description
```
Added value: +"distinct outlets in sources"
```

addedOutput schema / properties / data / items / properties / sourceCount

Added value: +{
+  "description": "entries in sources (one per page)",
+  "type": "integer"
+}

changedOutput schema / properties / data / items / required

Previous value: -[
-  "slug",
-  "url",
-  "headline",
-  "format",
-  "label",
-  "publishedAt",
-  "updatedAt",
-  "sources",
-  "attribution"
-]New value: +[
+  "slug",
+  "url",
+  "headline",
+  "format",
+  "label",
+  "publishedAt",
+  "updatedAt",
+  "sources",
+  "aiGenerated",
+  "attribution"
+]

First observedOct 7, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral fact — the searchable corpus is limited to published headlines and ledes, not full article text — which sets result expectations, but it says nothing about ranking, matching semantics, or pagination.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity shades into under-specification rather than pure conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but with 0% parameter coverage, no usage routing against the many sibling read tools, and only one sentence of behavior, the definition leaves real gaps for an agent deciding how to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters. The description implies a free-text 'query' but gives no syntax guidance (phrases, operators, stemming), and never mentions 'limit', its default of 10, or the maximum of 30.

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 (full-text search) and a specific resource with scope qualifiers: 'published headlines and ledes'. This is clearly distinguishable from get_story or get_latest by the act of searching, though no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives. The agent must infer that get_story handles single-story retrieval and get_latest handles recency, but the description never routes it.

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

All Minutes of AI 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?