Skip to main content
Glama
Sign In
Pubrio

Pubrio

Official
by pubrio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lookup_news

Retrieve detailed information for a news article using its unique search ID. Get specific article data from Pubrio's global business data layer.

Instructions

Look up detailed information about a specific news article by its search ID

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": {
      "news_search_id": "<news_search_id>"
    },
    "name": "lookup_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
news_search_idYesPubrio news search ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'detailed information' but does not specify what fields are returned, error handling (e.g., if ID not found), rate limits, authentication requirements, or any destructive nature. This is a significant gap for a tool with no annotation support.

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 a single concise sentence that accurately captures the tool's purpose without any unnecessary words. It is front-loaded and easy to parse.

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?

For a simple lookup tool with one parameter and no output schema, the description is minimally adequate. However, it lacks details about the return format or any constraints, which would be useful for an AI agent. Given the low complexity, a score of 3 seems fair.

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?

The only parameter, news_search_id, is described in the schema as 'Pubrio news search ID', and the description echoes that. Schema description coverage is 100%, so the description adds no additional meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 the verb 'look up', resource 'detailed information about a specific news article', and the method 'by its search ID'. It effectively distinguishes this from sibling tools like search_news (which retrieves summaries by criteria) and other lookup tools (lookup_company, etc.).

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 that a search_id is obtained from a prior search (e.g., search_news), but it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. The context is clear but lacks explicit guidance.

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

Deploy Server

Other Tools