Skip to main content
Glama
darrenjrobinson

Entra News MCP Server

get_issue

Retrieve complete newsletter content from the Entra.news archive by specifying an issue number or publication date. Access full text with preserved section headings for Microsoft Entra announcements and updates.

Instructions

Retrieve the full content of a specific Entra.news issue by issue number or publication date. Returns the complete text of the newsletter with section headings preserved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_numberNoIssue number (e.g. 42)
dateNoDate in YYYY-MM-DD or YYYY-MM format to find the nearest issue (e.g. "2024-03" or "2024-03-15")

Implementation Reference

  • The main handler function for the `get_issue` tool, which retrieves issue data by number or date and formats the response.
    export function handleGetIssue(args: GetIssueArgs): string {
      if (args.issue_number == null && !args.date) {
        return 'Please provide either an issue_number or a date to look up.';
      }
    
      let issue: Issue | null = null;
    
      if (args.issue_number != null) {
        issue = getIssueByNumber(args.issue_number);
        if (!issue) {
          return `Issue #${args.issue_number} not found in the archive.`;
        }
      } else if (args.date) {
        issue = getIssueByDate(args.date);
        if (!issue) {
          return `No issue found for date "${args.date}". Try a broader date range (e.g. just the year-month like "2024-03").`;
        }
      }
    
      if (!issue) return 'Issue not found.';
    
      const chunks = getChunksForIssue(issue.id);
      const fullText = chunks
        .map((c) => {
          const heading = c.section_heading ? `### ${c.section_heading}\n\n` : '';
          return `${heading}${c.text.trim()}`;
        })
        .join('\n\n');
    
      return formatIssue(issue, fullText || '*No content available for this issue.*');
    }
  • Input validation schema for the `get_issue` tool arguments.
    export const getIssueSchema = z.object({
      issue_number: z
        .number()
        .int()
        .positive()
        .optional()
        .describe('Issue number (e.g. 42)'),
      date: z
        .string()
        .optional()
        .describe('Date in YYYY-MM-DD or YYYY-MM format to find the nearest issue'),
    });
  • src/server.ts:45-64 (registration)
    Tool registration and definition for `get_issue` within the main server configuration.
    {
      name: 'get_issue',
      description:
        'Retrieve the full content of a specific Entra.news issue by issue number or publication date. ' +
        'Returns the complete text of the newsletter with section headings preserved.',
      inputSchema: {
        type: 'object',
        properties: {
          issue_number: {
            type: 'number',
            description: 'Issue number (e.g. 42)',
          },
          date: {
            type: 'string',
            description:
              'Date in YYYY-MM-DD or YYYY-MM format to find the nearest issue (e.g. "2024-03" or "2024-03-15")',
          },
        },
      },
    },
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses return format ('complete text of the newsletter with section headings preserved'), which compensates for missing output schema. Does not mention rate limits or auth, but return structure is the critical behavioral trait for this read operation.

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?

Two sentences with zero waste. First sentence covers purpose and identification methods; second covers return value. Front-loaded with action verb and efficiently structured.

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?

Given 2 parameters with 100% schema coverage and no output schema, the description appropriately explains return values ('complete text... section headings preserved'). No complex nested objects or annotations require additional explanation.

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 100%, establishing baseline 3. Description adds value by framing the parameters as alternatives ('issue number or publication date'), clarifying the OR relationship that the schema (with 0 required fields) doesn't explicitly convey.

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?

Description uses specific verb 'Retrieve' with resource 'Entra.news issue' and scope 'full content'. The word 'specific' effectively distinguishes this from sibling tools list_issues (plural/listing) and search_entra_news (searching).

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?

Implies usage by stating you retrieve 'by issue number or publication date', suggesting identifier-based lookup. However, lacks explicit when-to-use guidance contrasting with siblings (e.g., 'use this instead of search_entra_news when you need complete text').

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/darrenjrobinson/EntraNewsMCPServer'

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