smry Product

Create a durable query/news input

create_news_query

Destructive

Creates a Collection-compatible news query. Google News RSS is the current adapter and is intentionally hidden behind this durable product type. Example: {"query":"open source databases","collection":"Research"}

Input Schema

TableJSON Schema

Name	Required	Description
`query`	Yes
`locale`	No
`collection`	No	Collection id or name. A new name is created. Omit for Unsorted.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`object`	Yes
`followed`	Yes
`outcomes`	Yes
`collection`	Yes
`input_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 7, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / collection / anyOf

Previous value: -[
-  {
-    "anyOf": [
-      {
-        "default": 0,
-        "type": "string"
-      },
-      {
-        "maximum": 9007199254740991,
-        "minimum": 1,
-        "type": "integer"
-      }
-    ]
-  },
-  {
-    "maxLength": 100,
-    "minLength": 1,
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "maxLength": 100,
+    "minLength": 1,
+    "type": "string"
+  }
+]

removedOutput schema / properties / followed / anyOf

Removed value: -[
-  {
-    "default": 0,
-    "type": "string"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  }
-]

addedOutput schema / properties / followed / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / followed / minimum
```
Added value: +-9007199254740991
```
addedOutput schema / properties / followed / type
```
Added value: +"integer"
```

AddedSep 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already indicate a non-read-only, non-open-world operation, and the description adds that it hides the Google News RSS adapter behind a durable product type, which is useful abstraction context. However, it does not disclose side effects such as duplicate handling or whether the query becomes immediately available, leaving some behavioral gaps.

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 concise: two sentences and an example, with the core purpose front-loaded. Every word adds value; there is no filler or redundancy.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (3 parameters, output schema present), the description provides a good starting point but omits details like duplicate behavior, locale semantics, and the nature of the output (though the latter may be covered by the output schema). It is adequate but not fully complete.

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?

Schema description coverage is low (33%), covering only 'collection'. The description's example clarifies the usage of 'query' and 'collection' but says nothing about 'locale'. It partially compensates for the low coverage but leaves the 'locale' parameter's meaning undefined.

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 it creates a Collection-compatible news query, with a specific verb (creates) and resource (news query). It distinguishes itself from sibling tools by focusing on durable query creation, not on search or management. The mention of the hidden Google News RSS adapter adds implementation context, making the tool's role unmistakable.

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

Usage Guidelines3/5

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

The description implies the tool is for creating persistent news queries but does not explicitly contrast it with alternatives like search_article or query_feeds. It provides an example but lacks explicit guidance on when to use this tool versus others, nor any exclusions.

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

All smry Product 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?