Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

News Detail

news_detail
Read-onlyIdempotent

Retrieve the full text and complete details of a specific news article by its ID, obtained from news or news_search results.

Instructions

Get one news article's full detail by id (from news/news_search).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNews article ID (numeric), e.g. "7123456789012345678". Get IDs from `news` or `news_search`.
_jqNoOptional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / _jq / description
      Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "NewsAuthor": {
-      "properties": {
-        "avatar": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "NewsImage": {
-      "properties": {
-        "height": {
-          "format": "int32",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "url": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "width": {
-          "format": "int32",
-          "type": [
-            "integer",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "author": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/NewsAuthor"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "body": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "comments_count": {
-      "format": "int32",
-      "type": [
-        "integer",
-        "null"
-      ]
-    },
-    "description": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "id": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "images": {
-      "items": {
-        "$ref": "#/$defs/NewsImage"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "likes_count": {
-      "format": "int32",
-      "type": [
-        "integer",
-        "null"
-      ]
-    },
-    "published_at": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "shares_count": {
-      "format": "int32",
-      "type": [
-        "integer",
-        "null"
-      ]
-    },
-    "tickers": {
-      "items": {
-        "type": "string"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "title": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "url": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Addedv0.8.7

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, non-mutating operation. The description adds only that it fetches detail by ID, which is minimal extra context. It does not describe return format or error behavior, but with the annotation coverage, the description is not required to carry that burden. No contradiction exists.

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 sentence with zero filler. It immediately states the action, object, and prerequisite in a front-loaded manner. Every word earns its place; it is exemplary conciseness.

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?

For a simple get-by-id tool with only two parameters and no output schema, the description is sufficient: it clarifies what is returned ('full detail') and where to obtain the ID. It does not mention potential errors, but that is not necessary for such a straightforward tool. The inclusion of `news/news_search` provides critical routing context, making the tool complete for agent use.

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%: both `id` and `_jq` have detailed descriptions in the schema, including the format and source of the ID. The tool description does not add information beyond the schema, but with full coverage, the baseline of 3 is appropriate. No parameter is left unexplained.

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 states a specific verb ('Get'), a resource ('news article's full detail'), and the key parameter ('by id'). It also references `news/news_search` as the source of IDs, which clearly distinguishes this tool from those search/list siblings. An agent can immediately understand this is the detail-fetch counterpart to the search tools.

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

Usage Guidelines4/5

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

It explicitly says 'by id (from news/news_search)', which establishes the prerequisite condition for using this tool: you must already have an ID from the search tool. This implies that you use this tool when you have a specific article ID and need full details, versus using `news` or `news_search` to discover articles. However, it does not explicitly state 'when not to use this' or list alternative tools, so it is slightly below the strongest tier.

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