turva-mcp

Service catalog and pricing

get_services

Read-onlyIdempotent

Returns turva.dev's service catalog: the Shopify agent storefront check, agent-readiness audit, advisory, implementation, agent operations, and MCP server design, plus the engagement model and pricing (fixed list prices for the Shopify agent storefront check, audit, advisory and implementation; agent operations and MCP server design on request), and two implementation add-ons that carry a fixed price and are sold only with the diagnosis they follow, bought with it, with its report, or after the report and before implementation starts. Use this when a user asks what turva.dev offers, what it costs, or how an engagement works. For how to reach turva.dev use get_contact instead, and for the rules an engagement follows use get_principles. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`currency`	Yes
`services`	Yes
`engagement`	Yes
`pricing_note`	Yes
`vat_included`	Yes
`pricing_model`	Yes
`bundled_implementation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 23, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "bundled_implementation": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "price": {
+            "type": "number"
+          },
+          "requires": {
+            "description": "The id of the service this add-on is sold with.",
+            "type": "string"
+          },
+          "sold_separately": {
+            "type": "boolean"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "unit": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "price",
+          "unit",
+          "requires",
+          "sold_separately",
+          "summary"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "engagement": {
+      "additionalProperties": false,
+      "properties": {
+        "communication": {
+          "type": "string"
+        },
+        "notes": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "communication",
+        "notes"
+      ],
+      "type": "object"
+    },
+    "pricing_model": {
+      "type": "string"
+    },
+    "pricing_note": {
+      "type": "string"
+    },
+    "services": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "deliverable": {
+            "type": "string"
+          },
+          "duration": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "minimum_commitment": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "price": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "const": "on request",
+                "type": "string"
+              }
+            ],
+            "description": "EUR, VAT not included, or on request."
+          },
+          "sample_url": {
+            "description": "A published sample of the deliverable, where one exists.",
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "unit": {
+            "type": "string"
+          },
+          "url": {
+            "description": "The turva.dev page that describes the service.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "url",
+          "price",
+          "summary",
+          "deliverable"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "vat_included": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "pricing_model",
+    "pricing_note",
+    "currency",
+    "vat_included",
+    "engagement",
+    "services",
+    "bundled_implementation"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 29, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedJun 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the response is static JSON compiled into the Worker, changing nothing and updating only on deploy. It stops short of describing the response shape, which the output schema presumably carries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and routing sentences are front-loaded and efficient, but the pricing clause runs into a single dense, hard-to-parse construction about add-ons ('bought with it, with its report, or after the report and before implementation starts'). The information earns its place, but one sentence carries too much and hurts readability.

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 static catalog read with an output schema and full annotation coverage, the description supplies everything an agent needs: what it returns, when to call it, and which siblings to use instead. Return-value details are correctly delegated to the output schema.

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 and the schema explicitly forbids additional properties, so there is no parameter surface to document. Baseline 4 applies; the description correctly implies a no-argument read with no formatting options.

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 (returns turva.dev's service catalog and pricing) and enumerates the exact offerings, engagement model, and pricing structure. It explicitly distinguishes itself from siblings by naming get_contact and get_principles, so an agent can route correctly without opening a schema.

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?

Gives explicit trigger conditions ('when a user asks what turva.dev offers, what it costs, or how an engagement works') and names the two alternative tools with the conditions that select them. Nothing about when to prefer this tool is left to inference.

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

All turva-mcp tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?