get_request_optionsGet 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.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | Allowed product request platform/environment choices |
Changes observed during successful MCP inspections.
Output 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"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description adds real context beyond them: availability is administrator-configured, results may be narrower than capture options, and an empty list is a meaningful signal that submissions are disabled. Not a 5 because it says nothing about freshness, caching, or what the response structure looks like beyond IDs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Four short sentences, front-loaded with the resource definition and followed by the downstream usage, the narrowing caveat, and the empty-result semantics. Every sentence carries distinct information with no repetition of the title or schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read with an output schema and readOnlyHint coverage, the description supplies everything an agent needs: what the data is, how it differs from capture options, how to use the IDs, and the operational meaning of an empty result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the baseline is 4; there is no parameter semantics to explain and the description correctly does not attempt any. It does clarify that the meaningful payload is 'returned IDs', which primes the agent for how to consume output.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource (backend-defined platform/environment options for product requests) and contrasts them with capture options, so the agent knows this is a narrower, product-request-specific set. It does not name the obvious sibling (list_platforms) as an alternative, so differentiation is implied rather than explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes downstream usage: 'Use returned IDs in create_product_request,' which tells the agent this is a prerequisite lookup rather than a standalone query. It also gives a decision rule for empty results ('no platforms means new submissions are disabled'), but never states when to prefer this over list_platforms.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.