Skip to main content
Glama

open_catalog_form

Read-only

Open a Service Catalog item as an interactive request form in chat so users can fill variables, apply choices and lookups, and submit the request themselves.

Instructions

Open a Service Catalog item as an interactive request form inside the chat (Claude, ChatGPT, VS Code and other MCP Apps hosts). The user fills in the variables, with choices, reference lookups, variable sets and catalog UI policies applied, and submits the request themselves. Prefer this over asking the user for each variable. Pass the item sys_id or its name. Hosts without MCP Apps get the form definition as JSON.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item": "<item>"
    },
    "name": "open_catalog_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesCatalog item sys_id or name (e.g. "Standard Laptop")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that the user, not the agent, submits the request, that catalog UI policies, variable sets and reference lookups are applied, and that hosts without MCP Apps receive the raw form definition as JSON. That is meaningful behavior an agent could not infer from the schema.

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?

Three sentences, front-loaded with the action and ending with the important fallback caveat. Only the 'Pass the item sys_id or its name' clause duplicates the schema and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition covers what the tool does, who completes the action, what logic applies to the form, and how non-MCP-App hosts behave, which is sufficient for a single-parameter read tool with no output schema. It leaves open what the agent should do after submission.

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 coverage is 100% and the single parameter already documents 'sys_id or name' with an example. The description repeats that same instruction without adding format, resolution-order, or ambiguity-handling detail, so it lands at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Open a Service Catalog item as an interactive request form') and scopes it to the chat/MCP Apps host context. The phrase 'the user ... submits the request themselves' distinguishes it from the server-side ordering tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit preference rule: use this rather than interrogating the user for each variable. Context for use (interactive hosts) and the non-interactive fallback are both covered, though no exclusion such as when to use order_catalog_item instead is stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools