Skip to main content
Glama

Pollar News

Search Pollar News

search_news
Read-only

Searches Pollar's news archive using semantic and keyword matching. Use for any subject-specific query, including a person, organisation, place, or country (for example, interesting news in Poland). Put the subject or place in query. Locale controls response language, not geographic scope. For current headlines with no subject or place, use list_top_news.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYesFree-text search query
localeNoen

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
relatedYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "related": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "categoryPath": {
      +            "items": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "string"
      +              }
      +            ],
      +            "type": "array"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "imageSource": {
      +            "type": "string"
      +          },
      +          "imageUrl": {
      +            "type": "string"
      +          },
      +          "lead": {
      +            "type": "string"
      +          },
      +          "modifiedAt": {
      +            "type": "string"
      +          },
      +          "publishedAt": {
      +            "type": "string"
      +          },
      +          "shortHeadline": {
      +            "type": "string"
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "sourceCount": {
      +            "type": "number"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "format": "uri",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "slug",
      +          "title",
      +          "shortHeadline",
      +          "lead",
      +          "imageUrl",
      +          "imageSource",
      +          "publishedAt",
      +          "modifiedAt",
      +          "categoryPath",
      +          "sourceCount",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "results": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "categoryPath": {
      +            "items": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "string"
      +              }
      +            ],
      +            "type": "array"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "imageSource": {
      +            "type": "string"
      +          },
      +          "imageUrl": {
      +            "type": "string"
      +          },
      +          "lead": {
      +            "type": "string"
      +          },
      +          "modifiedAt": {
      +            "type": "string"
      +          },
      +          "publishedAt": {
      +            "type": "string"
      +          },
      +          "shortHeadline": {
      +            "type": "string"
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "sourceCount": {
      +            "type": "number"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "format": "uri",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "slug",
      +          "title",
      +          "shortHeadline",
      +          "lead",
      +          "imageUrl",
      +          "imageSource",
      +          "publishedAt",
      +          "modifiedAt",
      +          "categoryPath",
      +          "sourceCount",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "results",
      +    "related"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already provide readOnlyHint=true, confirming it's non-destructive. The description adds valuable behavioral context: it uses semantic and keyword matching, and locale controls response language not geographic scope. No contradictions with annotations.

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?

Description is concise and front-loaded. First sentence states the core purpose. Each subsequent sentence adds value: usage guidance, locale clarification, and sibling distinction. No unnecessary words.

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

Completeness5/5

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

Given the tool has 3 parameters (1 required) and an output schema exists, the description covers key aspects: subject-specific query usage, language vs geography scope, and when to use an alternative. The return format is covered by the output schema. No significant gaps.

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

Parameters4/5

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

Schema coverage is only 33% (only 'query' has a description). The description compensates by adding context: 'Put the subject or place in query' for the query parameter, and 'Locale controls response language, not geographic scope' for locale. No additional guidance for limit, but overall adds meaningful semantics beyond schema.

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?

Description clearly states the tool searches Pollar's news archive using semantic and keyword matching. It distinguishes itself from siblings by explicitly mentioning to use list_top_news for headlines without a specific subject or place, and clarifies that locale controls language, not geography.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use: for any subject-specific query (person, organization, place, country). Specifies what to put in the query and clarifies locale's role. Explicitly names alternative tool 'list_top_news' for current headlines without a subject.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources