list_threadsLists Pollar's active evergreen threads: ongoing storylines tracked over time and grouped by section, with the latest change magnitude. Suited to discovering long-running topics; get_thread takes a returned id for the detail.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | en |
| Name | Required | Description | Default |
|---|---|---|---|
| threads | Yes | ||
| sections | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / threads / items / properties / provenanceAdded value: +{
+ "additionalProperties": false,
+ "properties": {
+ "aiGenerated": {
+ "type": "boolean"
+ },
+ "editorialReview": {
+ "enum": [
+ "automated",
+ "human"
+ ],
+ "type": "string"
+ },
+ "label": {
+ "type": "string"
+ },
+ "machineTranslated": {
+ "type": "boolean"
+ },
+ "policyUrl": {
+ "format": "uri",
+ "type": "string"
+ }
+ },
+ "required": [
+ "aiGenerated",
+ "editorialReview",
+ "policyUrl",
+ "label"
+ ],
+ "type": "object"
+}Output schema / properties / threads / items / requiredPrevious value: -[
- "id",
- "section",
- "name",
- "thesis",
- "changeMagnitude",
- "magnitudeReason",
- "lastTickAt",
- "entryCount",
- "url"
-]New value: +[
+ "id",
+ "section",
+ "name",
+ "thesis",
+ "changeMagnitude",
+ "magnitudeReason",
+ "lastTickAt",
+ "entryCount",
+ "url",
+ "provenance"
+]Output schema / properties / sections / additionalProperties / properties / generatedAt / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / sections / additionalProperties / properties / generatedAt / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / sections / additionalProperties / properties / summary / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / sections / additionalProperties / properties / summary / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / threads / items / properties / changeMagnitude / anyOfRemoved value: -[
- {
- "type": "number"
- },
- {
- "type": "null"
- }
-]Output schema / properties / threads / items / properties / changeMagnitude / typeAdded value: +[
+ "number",
+ "null"
+]Output schema / properties / threads / items / properties / lastTickAt / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / threads / items / properties / lastTickAt / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / threads / items / properties / magnitudeReason / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / threads / items / properties / magnitudeReason / typeAdded value: +[
+ "string",
+ "null"
+]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, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaning beyond that: only *active* threads are returned, they are grouped by section, and each carries a 'latest change magnitude' — useful output-shape context. It omits auth, rate limits, and pagination behavior, keeping it out of the 5 band.
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 sentences, zero waste: the first defines what is listed and its shape, the second routes to the sibling. The primary purpose is front-loaded before the alternative is mentioned.
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?
An output schema exists, so the description needn't explain return values, and annotations cover safety. Purpose, sibling routing, and return characteristics are all present; only the locale parameter's effect on output language and any pagination/count limits are unaddressed.
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?
Schema description coverage is 0%, so the description would need to compensate for the single locale parameter — and it says nothing about locale. However, the parameter is a self-evident language enum with a default, so ambiguity is low and the schema still conveys the constraint. Baseline 3 reflects an undocumented but low-risk parameter.
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 states a specific verb (Lists) and resource (Pollar's active evergreen threads), and defines the concept as 'ongoing storylines tracked over time and grouped by section, with the latest change magnitude.' It also distinguishes itself from the sibling get_thread, so an agent can tell the two apart without opening either schema.
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?
'Suited to discovering long-running topics; get_thread takes a returned id for the detail' gives clear context for when to use this tool and names the alternative for detail retrieval. It stops short of explicit when-not conditions (e.g., inactive or historical threads), but the routing is unambiguous.
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.