Skip to main content
Glama
rp4

IIA-MCP Server

by rp4

get_standard_details

Retrieve detailed information about a specific IIA standard by providing its standard number. Access professional standards, guidance documents, and compliance validation resources through the IIA-MCP Server.

Instructions

Get detailed information about a specific IIA standard

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
standardNumberYesIIA standard number (e.g., "2010", "1100")

Implementation Reference

  • The primary handler function for the 'get_standard_details' tool. It searches the pre-built document index for documents matching the given standardNumber, retrieves the full content, and returns a formatted MCP response with the standard details.
    private async getStandardDetails(standardNumber: string): Promise<any> {
      const matchingDocs = Array.from(this.documentIndex.entries())
        .filter(([_, metadata]) => metadata.standardNumber === standardNumber);
    
      if (matchingDocs.length === 0) {
        return {
          content: [
            {
              type: 'text',
              text: `Standard ${standardNumber} not found in the repository.`,
            },
          ],
        };
      }
    
      const [filePath, metadata] = matchingDocs[0];
      const content = await this.getDocumentContent(filePath);
    
      return {
        content: [
          {
            type: 'text',
            text: `# ${metadata.title}\n**Standard:** ${standardNumber}\n**Category:** ${metadata.category}\n**Last Updated:** ${metadata.lastUpdated}\n\n${content}`,
          },
        ],
      };
    }
  • The tool registration entry in the listTools response, defining the name, description, and input schema for 'get_standard_details'.
    {
      name: 'get_standard_details',
      description: 'Get detailed information about a specific IIA standard',
      inputSchema: {
        type: 'object',
        properties: {
          standardNumber: {
            type: 'string',
            description: 'IIA standard number (e.g., "2010", "1100")',
          },
        },
        required: ['standardNumber'],
      },
    },
  • The input schema definition for the 'get_standard_details' tool, specifying the required 'standardNumber' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        standardNumber: {
          type: 'string',
          description: 'IIA standard number (e.g., "2010", "1100")',
        },
      },
      required: ['standardNumber'],
    },
  • The dispatch handler in the CallToolRequestSchema that routes to the getStandardDetails method.
    case 'get_standard_details':
      return this.getStandardDetails(args.standardNumber);
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 but offers minimal information. It implies a read-only operation ('Get') but doesn't address permissions, rate limits, error conditions, or response format. For a tool with zero annotation coverage, this is insufficient behavioral context.

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 wasted words. It's appropriately sized and front-loaded, 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.

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 (one parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage guidelines, behavioral traits, and output, which would be needed for higher completeness in a real-world scenario.

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, fully documenting the single parameter 'standardNumber' with examples. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 where 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 ('Get') and resource ('detailed information about a specific IIA standard'), making it immediately understandable. However, it doesn't differentiate this tool from its siblings (like 'get_document_updates' or 'get_related_documents'), which would require explicit comparison to achieve 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. It doesn't mention prerequisites, appropriate contexts, or exclusions, leaving the agent to infer usage from the tool name alone. This lack of explicit guidance is a significant gap.

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