Skip to main content
Glama
ogbm77

Cisco CX Cloud MCP Server

by ogbm77

get_field_notices

Retrieve important product notifications and bulletins for a specific customer to stay informed about critical updates and advisories.

Instructions

Get field notices for a specific customer. Returns important product notifications and bulletins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesThe customer ID

Implementation Reference

  • Handler for the get_field_notices tool: validates customerId input, calls makeApiCall to the /product-alerts/field-notices endpoint, and returns JSON-formatted response as text content.
    case "get_field_notices": {
      const customerId = args?.customerId as string;
      if (!customerId) {
        throw new Error("customerId is required");
      }
      const data = await makeApiCall("/product-alerts/field-notices", customerId);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:164-177 (registration)
    Registration of the get_field_notices tool in the tools array used for ListTools, including name, description, and input schema requiring customerId.
    {
      name: "get_field_notices",
      description: "Get field notices for a specific customer. Returns important product notifications and bulletins.",
      inputSchema: {
        type: "object",
        properties: {
          customerId: {
            type: "string",
            description: "The customer ID",
          },
        },
        required: ["customerId"],
      },
    },
  • Input schema for get_field_notices tool, defining customerId as required string.
    inputSchema: {
      type: "object",
      properties: {
        customerId: {
          type: "string",
          description: "The customer ID",
        },
      },
      required: ["customerId"],
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool returns 'important product notifications and bulletins,' which implies a read-only operation, but does not specify permissions, rate limits, error handling, or response format. For a tool with zero annotation coverage, this is inadequate, scoring 2 for lacking essential behavioral details.

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 appropriately sized and front-loaded: two concise sentences that directly state the tool's purpose and return value without waste. Every sentence earns its place by conveying essential information efficiently, warranting a score of 5.

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

Completeness3/5

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

Given the tool's low complexity (1 parameter, 100% schema coverage, no output schema), the description is minimally complete. It covers the basic purpose and return type but lacks behavioral details, usage guidelines, and output specifics. With no annotations and simple schema, it meets the bare minimum, scoring 3 as adequate but with clear gaps.

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?

The description does not add meaning beyond the input schema, which has 100% coverage for the single parameter 'customerId.' The schema already describes it as 'The customer ID,' so the baseline is 3. No additional parameter context is provided in the description, keeping it at the minimum viable score.

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 tool's purpose: 'Get field notices for a specific customer' specifies the verb (get) and resource (field notices), with scope (for a specific customer). It distinguishes from siblings like get_security_advisories or get_hardware_eol by focusing on product notifications and bulletins, though not explicitly contrasting them. A 5 would require explicit sibling differentiation.

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. It mentions 'for a specific customer' but does not clarify prerequisites, exclusions, or when to choose this over other tools like get_security_advisories. Without any usage context or alternatives named, it scores 2 for minimal guidance.

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/ogbm77/cisco-cx-cloud-mcp'

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