Skip to main content
Glama
rp4

IIA-MCP Server

by rp4

get_document_updates

Track updates to IIA documents by category and date to stay informed on standards, guidance, topics, and glossary changes.

Instructions

Check for recent updates to IIA documents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category
sinceNoISO date string to check for updates since

Implementation Reference

  • The main handler function that implements the get_document_updates tool logic, filtering documents by lastUpdated date and optional category, sorting by recency, and formatting the results.
    private async getDocumentUpdates(since?: string, category?: string): Promise<any> {
      const cutoffDate = since ? new Date(since) : new Date(Date.now() - 30 * 24 * 60 * 60 * 1000); // 30 days ago
      
      const updates = Array.from(this.documentIndex.entries())
        .filter(([_, metadata]) => {
          if (category && metadata.category !== category) return false;
          return new Date(metadata.lastUpdated) > cutoffDate;
        })
        .sort((a, b) => new Date(b[1].lastUpdated).getTime() - new Date(a[1].lastUpdated).getTime());
    
      const formattedUpdates = updates.map(([filePath, metadata]) => 
        `**${metadata.title}** (${metadata.category})\nUpdated: ${new Date(metadata.lastUpdated).toLocaleDateString()}\nFile: ${filePath}`
      ).join('\n\n');
    
      return {
        content: [
          {
            type: 'text',
            text: `Recent updates since ${cutoffDate.toLocaleDateString()}:\n\n${formattedUpdates || 'No recent updates found.'}`,
          },
        ],
      };
    }
  • Defines the input schema and metadata for the get_document_updates tool in the ListTools response.
      name: 'get_document_updates',
      description: 'Check for recent updates to IIA documents',
      inputSchema: {
        type: 'object',
        properties: {
          since: {
            type: 'string',
            description: 'ISO date string to check for updates since',
          },
          category: {
            type: 'string',
            description: 'Filter by category',
            enum: ['standards', 'guidance', 'topics', 'glossary'],
          },
        },
      },
    },
  • Registers the tool handler by dispatching to getDocumentUpdates method in the CallToolRequestSchema switch statement.
    case 'get_document_updates':
      return this.getDocumentUpdates(args.since, args.category);
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 only states what the tool does ('Check for recent updates') without explaining any behavioral traits like what 'recent' means, if there are rate limits, authentication needs, or how updates are determined. This leaves significant gaps in understanding the tool's 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?

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 tool's complexity (checking updates with parameters) and lack of annotations and output schema, the description is incomplete. It doesn't explain what 'updates' entail, the return format, or any behavioral context, leaving the agent with insufficient information to fully utilize the tool.

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 input schema has 100% description coverage, clearly documenting both parameters ('category' with enum values and 'since' as an ISO date). The description adds no additional meaning beyond this, as it doesn't elaborate on parameter usage or constraints. This meets the baseline score when schema coverage is high.

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 with a specific verb ('Check') and resource ('recent updates to IIA documents'), making it understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_related_documents' or 'search_documents', which might also involve document retrieval, so it doesn't achieve full 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. It doesn't mention any context, exclusions, or comparisons to sibling tools such as 'search_documents' or 'get_standard_details', leaving the agent with no usage instructions beyond the basic purpose.

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

Related 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/rp4/IIA-MCP'

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