list_threadsLists Pollar's active evergreen threads: ongoing storylines tracked over time and grouped by section, with the latest change magnitude. Use to discover long-running topics. Pass a returned id to get_thread for detail.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | en |
| Name | Required | Description | Default |
|---|---|---|---|
| threads | Yes | ||
| sections | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "sections": {
+ "additionalProperties": {
+ "additionalProperties": false,
+ "properties": {
+ "generatedAt": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "summary": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "summary",
+ "generatedAt"
+ ],
+ "type": "object"
+ },
+ "propertyNames": {
+ "type": "string"
+ },
+ "type": "object"
+ },
+ "threads": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "changeMagnitude": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "entryCount": {
+ "type": "number"
+ },
+ "id": {
+ "type": "string"
+ },
+ "lastTickAt": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "magnitudeReason": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "section": {
+ "enum": [
+ "europe",
+ "world",
+ "other"
+ ],
+ "type": "string"
+ },
+ "thesis": {
+ "type": "string"
+ },
+ "url": {
+ "format": "uri",
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "section",
+ "name",
+ "thesis",
+ "changeMagnitude",
+ "magnitudeReason",
+ "lastTickAt",
+ "entryCount",
+ "url"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "threads",
+ "sections"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the description adds behavioral context by describing the nature of returned data (threads grouped by section with latest change magnitude). Does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no fluff. First sentence defines behavior, second gives usage advice. Front-loaded with the verb and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, return values are covered. The description includes sufficient context about the list content and how to use results. However, the missing locale explanation reduces completeness for parameter usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'locale' has no description in schema (0% coverage), and the tool description does not mention it. The agent cannot infer that locale filters by language despite enum values. This is a significant gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Lists' and the resource 'Pollar's active evergreen threads', explaining that they are ongoing storylines grouped by section with change magnitude. It distinguishes from the sibling tool get_thread by suggesting chaining.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit usage guidance: 'Use to discover long-running topics' and recommends passing a returned id to get_thread for detail. Lacks explicit exclusion of alternatives when not to use, but the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.