Skip to main content
Glama
sorodriguezz

IRIS ObjectScript MCP Server

by sorodriguezz

open_class

Open InterSystems IRIS ObjectScript class documentation to view properties, methods, and usage examples for development reference.

Instructions

Abre Documatic por nombre de clase (ej. %Library.String).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
classYesClass name

Implementation Reference

  • Handler function for the "open_class" tool. Extracts the class name from input arguments, validates it, fetches the class documentation using fetchClassDoc, and returns the documentation text in the required MCP response format.
    case "open_class": {
      const className = args?.class as string;
      if (!className) {
        throw new Error("Class name is required");
      }
    
      const doc = await fetchClassDoc(className);
      return {
        content: [
          {
            type: "text",
            text: doc.text,
          },
        ],
      };
    }
  • Tool definition including the name, description, and input schema specifying a required 'class' string parameter with minimum length 3.
    export const OPEN_CLASS: Tool = {
      name: "open_class",
      description: "Abre Documatic por nombre de clase (ej. %Library.String).",
      inputSchema: {
        type: "object",
        properties: {
          class: {
            type: "string",
            description: "Class name",
            minLength: 3,
          },
        },
        required: ["class"],
      },
    };
  • Registration of core tools list, including OPEN_CLASS, exported as coreTools for use in server tool listing.
    export const coreTools = async () => {
      return {
        tools: [SMART_SEARCH, SEARCH_OBJECTSCRIPT, OPEN_BY_KEY, OPEN_CLASS],
      };
    };
  • src/server.ts:36-39 (registration)
    Server request handler registrations: ListToolsRequestSchema to coreTools (which lists open_class), and CallToolRequestSchema to callShema (which handles calls to open_class).
    server.setRequestHandler(ListToolsRequestSchema, coreTools);
    
    server.setRequestHandler(CallToolRequestSchema, callShema);
  • Import of the OPEN_CLASS tool definition into core.tool.ts for inclusion in the tools list.
    import { OPEN_CLASS } from "./open-class.tool.js";
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('Abre') but doesn't disclose behavioral traits such as what 'Documatic' refers to (e.g., a documentation system), whether it requires authentication, rate limits, or what happens if the class doesn't exist. This leaves significant gaps for a tool with no annotation coverage.

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 with zero waste, front-loaded with the core action and including a helpful example. It's appropriately sized for a simple tool with one parameter.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'Documatic' is, what the tool returns (e.g., documentation content, a link, or an error), or behavioral aspects like error handling. For a tool with minimal structured data, this lacks necessary context.

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?

Schema description coverage is 100%, with the parameter 'class' documented as 'Class name' and a minLength constraint. The description adds an example ('ej. %Library.String') which provides context on format, but doesn't add substantial meaning beyond what the schema already provides. Baseline 3 is appropriate given high schema coverage.

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 verb ('Abre' = Open) and resource ('Documatic por nombre de clase'), specifying it opens documentation for a class by name. It distinguishes from siblings by focusing on class names rather than keys or searches, though the distinction could be more explicit.

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?

No explicit guidance on when to use this tool versus alternatives like 'open_by_key', 'search_objectscript', or 'smart_search'. The description implies usage for opening documentation by class name, but lacks context on prerequisites, exclusions, or comparison to siblings.

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/sorodriguezz/iris-mcp-intelligence'

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