Skip to main content
Glama

Get product request options

get_request_options
Read-only

Get backend-defined platform/environment options for product requests. These may be narrower than capture options. Use returned IDs in create_product_request. Availability is configured by administrators; no platforms means new submissions are disabled.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_request_options"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
platformsYesResult entries

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • changedOutput schema / description
      Previous value: -"Structured result. Existing text or image content remains available in content."New value: +"Allowed product request platform/environment choices"
    • addedOutput schema / properties / platforms
      Added value: +{
      +  "description": "Result entries",
      +  "items": {
      +    "$ref": "#/$defs/platformOption"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Allowed product request platform/environment choices",
      -  "properties": {
      -    "platforms": {
      -      "description": "Result entries",
      -      "items": {
      -        "$ref": "#/$defs/platformOption"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "platforms"
      -  ],
      -  "type": "object"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "platforms"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "environmentOption": {
      +      "additionalProperties": true,
      +      "description": "Backend environment option",
      +      "properties": {
      +        "id": {
      +          "description": "id",
      +          "type": "string"
      +        },
      +        "label": {
      +          "description": "label",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "label"
      +      ],
      +      "type": "object"
      +    },
      +    "platformOption": {
      +      "additionalProperties": true,
      +      "description": "Backend platform option",
      +      "properties": {
      +        "environments": {
      +          "description": "Result entries",
      +          "items": {
      +            "$ref": "#/$defs/environmentOption"
      +          },
      +          "type": "array"
      +        },
      +        "id": {
      +          "description": "id",
      +          "type": "string"
      +        },
      +        "label": {
      +          "description": "label",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "label",
      +        "environments"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "description": "Structured result. Existing text or image content remains available in content.",
      +  "properties": {
      +    "result": {
      +      "additionalProperties": true,
      +      "description": "Allowed product request platform/environment choices",
      +      "properties": {
      +        "platforms": {
      +          "description": "Result entries",
      +          "items": {
      +            "$ref": "#/$defs/platformOption"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "platforms"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real context beyond that: the option set is administrator-configured, is a subset of capture options, and an empty result disables new submissions. That last detail meaningfully changes how an agent interprets an empty response, though fixed/static nature and result stability are not addressed.

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?

Three short sentences, front-loaded with the purpose and followed by the actionable ID handoff and the edge-case meaning. No sentence restates the title or the annotations, and nothing could be removed without losing information.

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?

With an output schema present, the description need not describe return values, and it covers the decision-relevant behavior for a zero-parameter read. What's missing is only marginal: whether the option list is stable across calls and how it relates to the similarly named platform siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The absence of parameters is consistent with the description's framing of a fixed, server-defined option list.

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?

States a specific verb and resource ("Get backend-defined platform/environment options for product requests") and scopes it against a related concept ("may be narrower than capture options"). It doesn't name a concrete sibling such as list_platforms or get_platform_summary, so the agent must still infer the boundary, which keeps it below a 5.

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?

Gives a clear downstream action ("Use returned IDs in create_product_request") and a blocking condition ("no platforms means new submissions are disabled"). It lacks an explicit statement of when to prefer get_platform_summary or list_platforms instead, so the when-not side is only partially covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources