Trusteed Agentic Commerce

get_store_trust

Read-onlyIdempotent

Get Demo Store's signed trust score (v4.1, 0-100) with per-signal data quality, confidence level, and a detached JWS for offline verification. Don't trust the number — verify it: download the JWKS at jwks_snapshot_uri, validate jws_compact with signing_kid, and recompute payload_hash_sha256.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`score`	Yes
`available`	Yes
`breakdown`	Yes
`issued_at`	Yes
`score_cap`	Yes
`signature`	Yes
`store_slug`	Yes
`computed_at`	Yes
`scoring_version`	Yes
`confidence_level`	Yes
`recommended_action`	Yes
`confidence_interval`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

addedOutput schema / properties / score_cap

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {
+        "applies": {
+          "type": "boolean"
+        },
+        "note": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "reason_code": {
+          "type": "string"
+        },
+        "uncapped_score": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "value": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "value",
+        "applies",
+        "uncapped_score",
+        "reason_code",
+        "note"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "store_slug",
-  "available",
-  "score",
-  "confidence_level",
-  "scoring_version",
-  "issued_at",
-  "computed_at",
-  "breakdown",
-  "signature",
-  "confidence_interval",
-  "recommended_action"
-]New value: +[
+  "store_slug",
+  "available",
+  "score",
+  "confidence_level",
+  "scoring_version",
+  "issued_at",
+  "computed_at",
+  "score_cap",
+  "breakdown",
+  "signature",
+  "confidence_interval",
+  "recommended_action"
+]

Changed2 schema fields changedOct 27, 2026

addedOutput schema / properties / computed_at

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "store_slug",
-  "available",
-  "score",
-  "confidence_level",
-  "scoring_version",
-  "issued_at",
-  "breakdown",
-  "signature",
-  "confidence_interval",
-  "recommended_action"
-]New value: +[
+  "store_slug",
+  "available",
+  "score",
+  "confidence_level",
+  "scoring_version",
+  "issued_at",
+  "computed_at",
+  "breakdown",
+  "signature",
+  "confidence_interval",
+  "recommended_action"
+]

Changed2 schema fields changedOct 10, 2026

addedOutput schema / properties / recommended_action

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {
+        "action": {
+          "enum": [
+            "proceed",
+            "proceed_with_human_confirmation",
+            "do_not_proceed"
+          ],
+          "type": "string"
+        },
+        "derived_from": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "reason_code": {
+          "enum": [
+            "below_eligibility_threshold",
+            "limited_history",
+            "established_record",
+            "unrecognized_confidence_level"
+          ],
+          "type": "string"
+        },
+        "signed": {
+          "const": false,
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "action",
+        "reason_code",
+        "derived_from",
+        "signed"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "store_slug",
-  "available",
-  "score",
-  "confidence_level",
-  "scoring_version",
-  "issued_at",
-  "breakdown",
-  "signature",
-  "confidence_interval"
-]New value: +[
+  "store_slug",
+  "available",
+  "score",
+  "confidence_level",
+  "scoring_version",
+  "issued_at",
+  "breakdown",
+  "signature",
+  "confidence_interval",
+  "recommended_action"
+]

AddedSep 25, 2026
RemovedSep 1, 2026
Changed2 schema fields changedAug 24, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / properties
```
Added value: +{}
```
AddedJul 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world; the description goes further by disclosing the payload's structure, that the JWS is detached, and the exact offline verification path including key discovery and hash recomputation. That is real behavioral context an agent could not infer from the annotation block.

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, both load-bearing: the first defines the payload, the second is a front-loaded imperative verification sequence. No filler and no restating of the tool name.

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 enumerate return fields, yet it usefully summarizes them and supplies the verification workflow. The only missing piece for full completeness is any guidance on failure modes or when the score is unavailable versus when a receipt should be fetched instead.

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 the baseline is 4; the description correctly adds nothing parameter-related and instead spends its words on output semantics. Nothing in the description misrepresents the empty input contract.

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 a specific verb and resource ('Get Demo Store's signed trust score') and immediately qualifies it with version, scale (v4.1, 0-100), and the bundled artifacts (per-signal data quality, confidence level, detached JWS). This clearly separates it from receipt-oriented siblings like get_trust_receipt and verify_trust_receipt, which operate on receipts rather than the score itself.

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 concrete usage posture ('Don't trust the number — verify it') and a three-step verification recipe pointing at jwks_snapshot_uri, signing_kid, and payload_hash_sha256. It does not, however, say when to prefer this over get_trust_receipt or verify_trust_receipt, so sibling routing is left implicit.

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

All Trusteed Agentic Commerce 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?