Skip to main content
Glama
nubiia-dev

MCP NewsAPI.ai

by nubiia-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

suggest_concepts

Read-only

Resolve a name to concept URIs (people, organisations, places, Wikipedia topics). Pass the returned uri as concept_uris to search_articles / search_events — much more precise than a keyword. Does not consume search tokens.

Instructions

Resolve a name to concept URIs (people, organisations, places, Wikipedia topics). Pass the returned uri as concept_uris to search_articles / search_events — much more precise than a keyword. Does not consume search tokens. Sorted by prominence in the news; check type and label to pick the right homonym.

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the prefix, ISO 639-3 (default eng).
pageNoResult page, from 1 (default 1).
countNoMax suggestions, 1-50 (default 10).
typesNoRestrict to these concept kinds (default: all). Accepts a single string or an array of strings.
prefixYesText typed so far (a name or the start of one), e.g. "Telef" or "bbc".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.2
    • addedInput schema / properties / types / anyOf
      Added value: +[
+  {
+    "enum": [
+      "person",
+      "loc",
+      "org",
+      "wiki"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "person",
+        "loc",
+        "org",
+        "wiki"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / types / description
      Previous value: -"Restrict to these concept kinds (default: all)."New value: +"Restrict to these concept kinds (default: all). Accepts a single string or an array of strings."
    • removedInput schema / properties / types / items
      Removed value: -{
-  "enum": [
-    "person",
-    "loc",
-    "org",
-    "wiki"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / types / type
      Removed value: -"array"
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds useful behavioral context: results are sorted by news prominence, and callers should inspect `type` and `label` to disambiguate homonyms. It does not mention pagination or result volume, but the core behavioral traits are well surfaced.

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 front-loaded with the core purpose, followed by precise downstream usage and a single disambiguation note. Every sentence adds signal, with no repetition or filler.

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?

For a read-only suggestion tool with full parameter schema coverage, the description covers the essential gaps: what the output is, how to use it, token behavior, ordering, and homonym handling. No output schema exists, but the returned fields are adequately described.

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?

Schema description coverage is 100%, so the five parameters are already well documented. The description adds only indirect guidance about the returned `uri`, `type`, and `label`, not the `prefix`, `lang`, `page`, `count`, or `types` inputs, so the baseline 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?

States a specific verb-resource pair: resolve a name to concept URIs, with the resource kinds enumerated (people, organisations, places, Wikipedia topics). This clearly distinguishes it from sibling suggestion tools like suggest_sources or suggest_categories.

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?

Explicitly says to pass the returned `uri` as `concept_uris` to search_articles / search_events and contrasts this with keyword search. It also states that the tool does not consume search tokens, giving a clear operational reason to use it.

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