SkoIA Parts

Get commerce discovery candidates

get_offers

Read-onlyIdempotent

Deprecated compatibility adapter. Returns provider discovery only; use get_verified_commerce_options for separated verified output.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`tool`	Yes
`facts`	Yes
`status`	Yes
`warnings`	Yes
`requestId`	Yes
`confidence`	Yes
`provenance`	Yes
`schemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 2, 2026
- addedOutput schema / properties / confidence / properties / score / anyOf
```
Added value: +[
+  {
+    "maximum": 1,
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / confidence / properties / score / maximum
```
Removed value: -1
```
- removedOutput schema / properties / confidence / properties / score / minimum
```
Removed value: -0
```
- removedOutput schema / properties / confidence / properties / score / type
```
Removed value: -"number"
```
First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark the tool read-only and idempotent. The description adds useful context beyond that: deprecation status, the restriction to provider discovery only, and the fact that verified output is intentionally separated.

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?

One short sentence front-loads the deprecation warning and immediately points to the replacement. No filler or repetition of the schema.

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?

For a deprecated adapter with safe read annotations and an output schema, the description covers selection, behavior, and alternative routing. It is slightly incomplete only in parameter semantics, which is already accounted for separately.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needed to explain query and limit semantics but does not mention either parameter. The agent must infer that query is the search text and limit caps the result count from the property names and constraints.

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?

States it is a deprecated compatibility adapter and explicitly says it returns provider discovery only, which distinguishes it from get_verified_commerce_options. The verb 'returns' plus resource scope makes the tool's function clear.

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

Usage Guidelines5/5

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

Names the alternative tool explicitly and gives the condition for it: 'use get_verified_commerce_options for separated verified output.' The 'Deprecated compatibility adapter' label tells agents to avoid this tool unless compatibility is required.

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

All SkoIA Parts 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?