Duoly

Find a teammate or coach

find_session

Read-onlyIdempotent

Start here to find a player or coach. Returns up to three matching sessions with real calculated prices, descriptions, missing inputs and bookUrls to open Duoly. Use exact game, goal, rank and region tokens; errors list valid choices.

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": {
      "game": "<game>"
    },
    "name": "find_session"
  }
}

Input Schema

Name	Required	Description
`game`	Yes	Game id or slug from list_games.
`goal`	No	Goal text matched by explicit keyword rules; use goalType to resolve ambiguity.
`mood`	No
`rank`	No
`role`	No	Exact role token from list_services, including Fill/Flex/Any for no preference.
`seats`	No	Hired teammates, excluding the customer and friends. Must match the service seat rule.
`voice`	No
`budget`	No	Maximum total price in the specified currency.
`region`	No	Exact server token, alias for server.
`server`	No
`edition`	No
`category`	No	Category token: duo, training, other; coaching and teams are aliases.
`currency`	No
`goalType`	No
`quantity`	No
`character`	No	One free-text character, only for character-bearing coaching services. Never use agent for this.

Output Schema

Name	Required	Description	Default
`game`	Yes
`notice`	Yes
`matches`	Yes
`budgetApplied`	Yes
`missingInputs`	Yes
`recommendation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026
- changedInput schema / properties / quantity / maximum
```
Previous value: -10New value: +5
```

Changed5 schema fields changedNov 7, 2026

addedInput schema / properties / character

Added value: +{
+  "description": "One free-text character, only for character-bearing coaching services. Never use agent for this.",
+  "maxLength": 40,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / mood

Added value: +{
+  "enum": [
+    "chill",
+    "tryhard",
+    "teach",
+    "fun"
+  ],
+  "type": "string"
+}

addedInput schema / properties / role

Added value: +{
+  "description": "Exact role token from list_services, including Fill/Flex/Any for no preference.",
+  "maxLength": 24,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / seats

Added value: +{
+  "description": "Hired teammates, excluding the customer and friends. Must match the service seat rule.",
+  "maximum": 5,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / voice
```
Added value: +{
+  "type": "boolean"
+}
```

Changed3 schema fields changedNov 7, 2026

changedInput schema / properties / goal / description

Previous value: -"Exact goal token: duo, coaching, ranked, casual or teams."New value: +"Goal text matched by explicit keyword rules; use goalType to resolve ambiguity."

addedInput schema / properties / goalType

Added value: +{
+  "enum": [
+    "climb",
+    "learn",
+    "learn_role",
+    "learn_character",
+    "review",
+    "mechanics",
+    "friends",
+    "casual",
+    "have_fun",
+    "play_tonight"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / recommendation

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "goal": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "serviceId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "serviceId",
+    "goal",
+    "reason"
+  ],
+  "type": "object"
+}

Changed11 schema fields changedNov 7, 2026

addedOutput schema / properties / matches / items / properties / bundleDiscountPercent
```
Added value: +{
+  "type": "number"
+}
```

removedOutput schema / properties / matches / items / properties / editions

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedOutput schema / properties / matches / items / properties / perUnitMinor

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / matches / items / properties / priceNote
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / matches / items / properties / ranks

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / matches / items / properties / regions

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedOutput schema / properties / matches / items / properties / representativePrice

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "amountMinor": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "bundleDiscountPercent": {
+      "type": "number"
+    },
+    "currency": {
+      "enum": [
+        "EUR",
+        "USD"
+      ],
+      "type": "string"
+    },
+    "perUnitMinor": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "quantity": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "rank": {
+      "type": "string"
+    },
+    "savingMinor": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "perUnitMinor",
+    "savingMinor",
+    "bundleDiscountPercent",
+    "quantity",
+    "amountMinor",
+    "currency"
+  ],
+  "type": "object"
+}

removedOutput schema / properties / matches / items / properties / requiredInputs

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedOutput schema / properties / matches / items / properties / savingMinor

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

removedOutput schema / properties / matches / items / properties / url
```
Removed value: -{
-  "format": "uri",
-  "type": "string"
-}
```

changedOutput schema / properties / matches / items / required

Previous value: -[
-  "id",
-  "name",
-  "category",
-  "description",
-  "fromPrice",
-  "unit",
-  "ranks",
-  "regions",
-  "editions",
-  "requiredInputs",
-  "bookUrl",
-  "url",
-  "priceKind",
-  "amountMinor",
-  "currency",
-  "formattedPrice",
-  "quantity",
-  "missingInputs"
-]New value: +[
+  "id",
+  "name",
+  "category",
+  "description",
+  "unit",
+  "bookUrl",
+  "priceNote",
+  "perUnitMinor",
+  "savingMinor",
+  "bundleDiscountPercent",
+  "priceKind",
+  "amountMinor",
+  "currency",
+  "formattedPrice",
+  "quantity",
+  "missingInputs"
+]

AddedNov 6, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: a hard cap of three results, inclusion of calculated prices and 'missing inputs' (partial-match signaling), bookUrls for handoff, and that validation errors enumerate valid choices. Annotations already cover the read-only/idempotent safety profile, so this extra context is genuine value.

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 tight sentences with the entry-point cue front-loaded and no filler. The second sentence is dense but each clause (count cap, prices, missing inputs, bookUrls) carries distinct information.

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

Completeness3/5

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

For a 16-parameter discovery tool with an output schema present, the description covers purpose, result cap and token discipline, which is the minimum an agent needs. Gaps remain around how the returned 'sessions' relate to booking flow and the many enum-valued parameters documented only by their schema enums.

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?

With 16 parameters and only ~50% schema description coverage, the description should compensate more than it does. It adds useful guidance about exact game/goal/rank/region tokens and error-driven choice discovery, but says nothing about several undescribed params (mood, rank, voice, edition, currency, goalType, quantity).

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?

Opens with a specific verb+resource ('find a player or coach') and describes the return shape: up to three matching sessions with prices, descriptions, missing inputs and bookUrls. This is clearly a search/discovery tool. It stops short of naming how it differs from siblings like get_availability or get_quote, which an agent must infer.

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

Usage Guidelines3/5

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

'Start here' signals entry-point usage, implying the agent should call this before deeper lookups, and the token guidance steers query formulation. However, no explicit alternatives or when-not conditions are given (e.g., when to prefer get_quote or get_availability after finding a session), so the routing must be inferred.

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

All Duoly tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?