Skip to main content
Glama
sorodriguezz

IRIS ObjectScript MCP Server

by sorodriguezz

search_objectscript

Find ObjectScript documentation and code examples from the local cache to help developers implement solutions quickly.

Instructions

Search for ObjectScript documentation and examples (solo en caché local)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query

Implementation Reference

  • Handler logic for the search_objectscript tool: extracts the query parameter, validates it, calls searchInCache, and returns formatted text results.
    case "search_objectscript": {
      const query = args?.q as string;
      if (!query) {
        throw new Error("Query is required");
      }
    
      const results = await searchInCache(query);
      return {
        content: [
          {
            type: "text",
            text: `Resultados de búsqueda para "${query}":\n\n${results}`,
          },
        ],
      };
    }
  • Tool definition including name, description, and input schema (JSON Schema) for the search_objectscript tool.
    export const SEARCH_OBJECTSCRIPT: Tool = {
      name: "search_objectscript",
      description:
        "Search for ObjectScript documentation and examples (solo en caché local)",
      inputSchema: {
        type: "object",
        properties: {
          q: {
            type: "string",
            description: "Search query",
            minLength: 2,
          },
        },
        required: ["q"],
      },
    };
  • Registers the SEARCH_OBJECTSCRIPT tool in the coreTools function that returns the list of available tools.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the cache limitation ('solo en caché local'), which is useful context about scope and data freshness. However, it doesn't describe important behavioral aspects like whether this is a read-only operation (implied but not stated), what format results return, whether there are rate limits, or authentication requirements. For a search tool with zero annotation coverage, this leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately concise with a single sentence that states the core purpose upfront. The parenthetical note about local cache adds important context without unnecessary elaboration. However, the Spanish phrase '(solo en caché local)' mixed with English might create minor clarity issues in some contexts, preventing a perfect score.

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 has no annotations, no output schema, and 1 parameter with good schema coverage, the description should provide more complete context. While it mentions the cache limitation, it doesn't explain what 'ObjectScript documentation and examples' encompasses, what format results return, or how this differs from sibling tools. For a search tool that presumably returns structured results, the lack of output information is a significant gap.

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 single parameter 'q' documented as 'Search query' with a minimum length constraint. The description doesn't add any parameter-specific information beyond what the schema provides. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in description, which applies here.

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 as searching for ObjectScript documentation and examples, using the specific verb 'search' with the resource 'ObjectScript documentation and examples'. It distinguishes from siblings like 'open_by_key' and 'open_class' by focusing on search functionality rather than direct access. However, it doesn't explicitly differentiate from 'smart_search', which might be a more advanced search alternative.

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 minimal guidance with the parenthetical note '(solo en caché local)', which suggests the search is limited to local cache only. However, it doesn't explain when to use this tool versus alternatives like 'smart_search', nor does it provide context about when this search approach is appropriate versus direct access tools. No explicit when/when-not guidance or alternative recommendations are included.

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