Skip to main content
Glama

Pollar News

Search Pollar News

search
Read-only

Searches Pollar's published news and returns a ranked list of matching articles as {id, title, url}. Suited to queries about a subject, person, organisation, place, or country, with that subject or place as the query. Locale controls response language, not geographic scope. fetch takes a returned id and returns the article.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesFree-text search query
localeNoen

Output Schema

NameRequiredDescriptionDefault
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": {
      +    "results": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "id": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "format": "uri",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "title",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "results"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint false), so the bar is lower, yet the description still adds the ranked-list return semantics and the important locale-behaviour rule. It does not describe result limits, ranking criteria, or empty-result behaviour, but it adds genuine context beyond the structured fields.

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?

Four short sentences, purpose and return shape front-loaded, followed by query guidance, locale semantics, and the handoff to fetch. The return-shape sentence partially duplicates the output schema, which is the only wasted content.

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

Completeness4/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 enumerated, and the description still covers purpose, query construction, locale semantics, and the follow-up tool. The one meaningful omission is sibling disambiguation against search_news and news_near.

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 50% because locale has an enum but no description; the description fills that gap by explaining locale controls response language rather than geographic scope. It also steers how query should be formed (subject, person, organisation, place, country), adding meaning beyond the schema's bare "Free-text search query".

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?

The description states a specific verb and resource ("Searches Pollar's published news") and names the return shape, so the operation is unambiguous. It implicitly separates itself from news_near by noting locale is language, not geography, but it never distinguishes itself from the near-identical sibling search_news, leaving one key identity question open.

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?

It gives useful positive guidance (queries about a subject, person, organisation, place, or country, with that subject as the query) and points to fetch as the follow-up step. However, it never states when to prefer this tool over search_news, list_top_news, or news_near, which is exactly the choice an agent faces with this sibling set.

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