Advisors AI — Route a Store Need to a Service

Prepare a normal request link for a selected package

advisors_order_prepare_link

Read-onlyIdempotent

Use only after the user explicitly selects a package returned by the service tool. Returns the ordinary login/request link; it does not create an order, confirm eligibility, or charge anything.

Input Schema

Name	Required	Description	Default
`language`	No	Request-page language: ar or en.	ar
`package_id`	Yes	Published package id returned by advisors_catalog_get_service.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`status`	Yes
`package`	Yes
`request_url`	Yes
`creates_order`	Yes
`charges_customer`	Yes
`attribution_status`	Yes
`eligibility_status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

addedOutput schema / $defs / PackageOutput / properties / price_status

Added value: +{
+  "anyOf": [
+    {
+      "const": "pending_approval",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Price Status"
+}

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond the annotations: it does not create an order, confirm eligibility, or charge anything, which reassures the agent about lack of side effects. Auth requirements and rate limits are still unmentioned, but are not critical here.

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?

Two sentences with zero waste. The first sentence front-loads the usage prerequisite, and the second sentence states the return and explicitly clarifies what the tool does not do.

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

Completeness5/5

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

For a low-complexity, read-only tool with rich annotations, a full input schema, and an output schema, the description covers what the agent needs: when to use it and what it does not do. Return value details are appropriately left to the output schema.

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%, so the schema already documents both parameters fully. The description adds minimal parameter meaning beyond linking package_id to a package returned by the service tool. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific action: returns the ordinary login/request link for a selected package. It distinguishes the tool from order creation, eligibility confirmation, and charging, but does not explicitly name sibling tools that might be alternatives.

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 a clear prerequisite: use only after the user explicitly selects a package returned by the service tool. It also states what the tool does not do, which implicitly rules out using it for order creation or eligibility checks, but no named alternative is provided for those cases.

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

All Advisors AI — Route a Store Need to a Service tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?