Skip to main content
Glama
sorodriguezz

IRIS ObjectScript MCP Server

by sorodriguezz

open_by_key

Access InterSystems IRIS ObjectScript documentation pages directly using their official document keys to find specific technical information quickly.

Instructions

Open a documentation page by its official KEY

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesDocument key

Implementation Reference

  • Handler logic for the 'open_by_key' tool: extracts 'key' from arguments, fetches document content using fetchDocByKey, and returns it as text content.
    case "open_by_key": {
      const key = args?.key as string;
      if (!key) {
        throw new Error("Key is required");
      }
    
      const content = await fetchDocByKey(key);
      return {
        content: [
          {
            type: "text",
            text: content.text,
          },
        ],
      };
    }
  • Tool definition including name, description, and input schema requiring a 'key' string.
    export const OPEN_BY_KEY: Tool = {
      name: "open_by_key",
      description: "Open a documentation page by its official KEY",
      inputSchema: {
        type: "object",
        properties: {
          key: {
            type: "string",
            description: "Document key",
            minLength: 3,
          },
        },
        required: ["key"],
      },
    };
  • Registration of the 'open_by_key' tool (as OPEN_BY_KEY) in the core tools array provided by coreTools function.
    export const coreTools = async () => {
      return {
        tools: [SMART_SEARCH, SEARCH_OBJECTSCRIPT, OPEN_BY_KEY, OPEN_CLASS],
      };
    };
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 action ('Open') but doesn't clarify what 'Open' means operationally (e.g., returns content, navigates, requires permissions) or any side effects. 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 that directly states the tool's function without unnecessary words. It is front-loaded and wastes no space, making it easy 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 no annotations and no output schema, the description is incomplete for a tool that presumably returns documentation content. It lacks details on behavior, output format, error handling, or dependencies, leaving the agent with insufficient context for reliable use.

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 schema description coverage is 100%, with the parameter 'key' documented as 'Document key' and a minLength constraint. The description adds minimal value by reinforcing 'official KEY' but doesn't provide additional context like format examples or where to find keys, so it meets the baseline for 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 action ('Open') and resource ('documentation page') with the specific mechanism ('by its official KEY'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'open_class' or 'search_objectscript', 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?

No guidance is provided on when to use this tool versus alternatives like 'open_class' or 'search_objectscript'. The description implies usage when you have a known document key, but it doesn't specify prerequisites, exclusions, or contextual alternatives.

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