Skip to main content
Glama
darrenjrobinson

Entra News MCP Server

find_tool_mentions

Discover community tools and open-source resources mentioned in Entra.news articles. Search by technology keyword to find GitHub projects, PowerShell tools, and their context within newsletter issues.

Instructions

Find community tools, GitHub projects, and open-source resources mentioned in Entra.news. Returns tool names, descriptions, GitHub URLs, and the issue context where they appeared. Optionally filter by keyword to find tools related to a specific technology or capability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional filter — search by tool name, technology, or description keyword (e.g. "PowerShell", "Conditional Access", "reporting")
limitNoMaximum number of tool mentions to return (default: 20)

Implementation Reference

  • The handler function that executes the "find_tool_mentions" tool logic by calling the database and formatting the output.
    export function handleFindToolMentions(args: FindToolMentionsArgs): string {
      const { query, limit } = args;
      const mentions = findToolMentions(query, limit);
    
      if (mentions.length === 0) {
        const qualifier = query ? ` mentioning "${query}"` : '';
        return `No content found${qualifier} in the archive.`;
      }
    
      const hasSynthetic = mentions.some((m) => m.id < 0);
      const header = query
        ? `## Entra.news mentions of "${query}"\n\n` +
          (hasSynthetic
            ? `_(No GitHub/Microsoft tool entries matched — showing issues where this term appears in content.)_\n\n`
            : '') +
          `Found ${mentions.length} result(s):\n\n---\n\n`
        : `## Community Tools Mentioned in Entra.news\n\n${mentions.length} mention(s):\n\n---\n\n`;
    
      const body = mentions.map((t, i) => formatToolMention(t, i + 1)).join('\n\n---\n\n');
      return header + body;
    }
  • The Zod schema definition for input validation of the "find_tool_mentions" tool.
    export const findToolMentionsSchema = z.object({
      query: z
        .string()
        .optional()
        .describe(
          'Optional search query — filter by tool name, technology, or description keyword'
        ),
      limit: z
        .number()
        .int()
        .min(1)
        .max(100)
        .default(20)
        .describe('Maximum number of tool mentions to return'),
    });
  • src/server.ts:96-116 (registration)
    The MCP tool registration for "find_tool_mentions" within the TOOLS array.
      name: 'find_tool_mentions',
      description:
        'Find community tools, GitHub projects, and open-source resources mentioned in Entra.news. ' +
        'Returns tool names, descriptions, GitHub URLs, and the issue context where they appeared. ' +
        'Optionally filter by keyword to find tools related to a specific technology or capability.',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description:
              'Optional filter — search by tool name, technology, or description keyword (e.g. "PowerShell", "Conditional Access", "reporting")',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of tool mentions to return (default: 20)',
            default: 20,
          },
        },
      },
    },
Behavior4/5

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

No annotations provided, so description carries full burden. Effectively discloses return structure ('Returns tool names, descriptions, GitHub URLs, and the issue context') compensating for missing output schema. Explains optional filtering behavior. Does not mention rate limits or auth requirements, but 'Find' implies safe read-only 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 well-structured sentences. First establishes purpose and return values; second explains optional filtering. Zero redundancy—every clause provides actionable information about scope or behavior. Appropriately front-loaded with the core action.

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 low-complexity tool (2 params, no nested objects, 100% schema coverage) lacking output schema, the description is complete. It explicitly documents the return payload structure (tool names, URLs, context) that would normally appear in an output schema, eliminating the need for additional behavioral description.

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 connecting the filtering concept to semantic use cases ('find tools related to a specific technology or capability'), helping agents understand the query parameter's purpose beyond syntax. Could explicitly name the 'limit' parameter, but schema handles this adequately.

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?

Specific verb 'Find' plus precise resource scope 'community tools, GitHub projects, and open-source resources mentioned in Entra.news'. Clearly distinguishes from siblings (get_issue, list_issues, search_entra_news) by focusing exclusively on tool mentions rather than general newsletter content.

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?

Provides clear contextual differentiation by specifying the tool searches for 'community tools, GitHub projects, and open-source resources', implicitly guiding users to select this when seeking tooling recommendations rather than general news. Lacks explicit 'use X instead for general searches' exclusion, but the scope is distinct enough to guide selection.

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