Skip to main content
Glama

get_news_detail

Retrieve detailed information for a specific news article from the N Lobby school portal, including content and optional read status updates.

Instructions

Retrieve detailed information for a specific news article

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
newsIdYesThe ID of the news article to retrieve
markAsReadNoMark the news article as read (optional, default: false)

Implementation Reference

  • MCP tool handler for get_news_detail: extracts newsId and optional markAsRead, calls api.getNewsDetail, optionally marks as read, returns JSON response or error message.
    case "get_news_detail":
      try {
        const { newsId, markAsRead = false } = args as {
          newsId: string;
          markAsRead?: boolean;
        };
    
        const newsDetail = await this.api.getNewsDetail(newsId);
    
        if (markAsRead) {
          try {
            await this.api.markNewsAsRead(newsId);
          } catch (markError) {
            logger.error(
              `Failed to mark news ${newsId} as read:`,
              markError,
            );
          }
        }
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(newsDetail, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error: ${error instanceof Error ? error.message : "Unknown error"}\n\nTo authenticate:\n1. Login to N Lobby in your browser\n2. Open Developer Tools (F12)\n3. Go to Application/Storage tab\n4. Copy cookies and use the set_cookies tool\n5. Use health_check to verify connection`,
            },
          ],
        };
      }
  • Input schema for get_news_detail tool: requires newsId (string), optional markAsRead (boolean, default false).
    name: "get_news_detail",
    description:
      "Retrieve detailed information for a specific news article",
    inputSchema: {
      type: "object",
      properties: {
        newsId: {
          type: "string",
          description: "The ID of the news article to retrieve",
        },
        markAsRead: {
          type: "boolean",
          description:
            "Mark the news article as read (optional, default: false)",
          default: false,
        },
      },
      required: ["newsId"],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions retrieving details and implies optional marking as read via the parameter, but fails to address critical aspects like authentication requirements, error handling, rate limits, or what 'detailed information' includes (e.g., fields returned). This leaves significant gaps for an agent to understand the tool's behavior.

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, efficient sentence that directly states the tool's function without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly, with every part contributing to the core purpose.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a tool that retrieves detailed data. It doesn't specify the format or content of the returned information, potential side effects (e.g., marking as read), or error conditions. For a retrieval tool with behavioral implications, this leaves the agent under-informed.

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 schema fully documents both parameters (newsId and markAsRead). The description adds no additional meaning beyond what's in the schema, such as explaining parameter interactions or providing examples. This meets the baseline for high schema coverage but doesn't enhance parameter understanding.

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 clearly states the verb 'retrieve' and the resource 'detailed information for a specific news article', making the purpose unambiguous. However, it doesn't explicitly differentiate from its sibling 'get_news' (which likely lists articles) or 'mark_news_as_read' (which handles read status updates), missing full sibling distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_news' or 'mark_news_as_read'. It lacks context about prerequisites (e.g., authentication needs) or exclusions, offering only a basic functional statement without usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/minagishl/nlobby-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server