Skip to main content
Glama
rp4

IIA-MCP Server

by rp4

get_related_documents

Locate relevant documents and implementation guidance for a specific topic or standard using the IIA-MCP Server, ensuring accurate audit compliance and resource access.

Instructions

Find documents related to a specific topic or standard

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeGuidanceNoInclude implementation guidance documents
topicYesTopic or standard to find related documents for

Implementation Reference

  • The core handler function that executes the get_related_documents tool. It searches for documents related to the given topic using searchDocuments and filters out guidance documents if includeGuidance is false.
    private async getRelatedDocuments(topic: string, includeGuidance: boolean = true): Promise<any> {
      const results = await this.searchDocuments(topic, undefined, 20);
      
      if (!includeGuidance) {
        // Filter out guidance documents
        const filteredResults = results.content[0].text.split('\n\n---\n\n')
          .filter(section => !section.includes('(guidance)'))
          .join('\n\n---\n\n');
        
        return {
          content: [
            {
              type: 'text',
              text: filteredResults,
            },
          ],
        };
      }
    
      return results;
    }
  • Registration of the get_related_documents tool in the ListTools response, including name, description, and input schema.
    {
      name: 'get_related_documents',
      description: 'Find documents related to a specific topic or standard',
      inputSchema: {
        type: 'object',
        properties: {
          topic: {
            type: 'string',
            description: 'Topic or standard to find related documents for',
          },
          includeGuidance: {
            type: 'boolean',
            description: 'Include implementation guidance documents',
            default: true,
          },
        },
        required: ['topic'],
      },
    },
  • Input schema defining the parameters for the get_related_documents tool: topic (required string) and includeGuidance (optional boolean).
    inputSchema: {
      type: 'object',
      properties: {
        topic: {
          type: 'string',
          description: 'Topic or standard to find related documents for',
        },
        includeGuidance: {
          type: 'boolean',
          description: 'Include implementation guidance documents',
          default: true,
        },
      },
      required: ['topic'],
    },
  • Dispatch case in the CallToolRequest handler that routes to the getRelatedDocuments method.
    case 'get_related_documents':
      return this.getRelatedDocuments(args.topic, args.includeGuidance);
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 what the tool does ('Find documents') but doesn't describe behavioral traits such as whether it's read-only, how results are returned (e.g., pagination, sorting), error conditions, or performance characteristics. This leaves significant gaps for an agent to understand how to use it effectively.

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 states the purpose clearly without unnecessary words. It's appropriately sized and front-loaded, with every word earning its place, making it easy for an agent to parse quickly.

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 (a search/retrieval operation with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'related' entails, the format or scope of returned documents, or any limitations (e.g., result count, sorting). This leaves the agent with insufficient context to use the tool correctly without trial and error.

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, so the schema already documents both parameters ('topic' and 'includeGuidance') adequately. The description adds no additional meaning beyond what's in the schema, such as examples of topics or clarification on what 'related' means. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Find') and resource ('documents'), and specifies the scope ('related to a specific topic or standard'). However, it doesn't explicitly differentiate from sibling tools like 'search_documents' or 'get_document_updates', which prevents a perfect score.

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 'search_documents' or 'get_standard_details'. It mentions the general context ('related to a specific topic or standard') but offers no explicit when/when-not instructions or comparisons to sibling tools.

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