Skip to main content
Glama

Service catalog and pricing

get_services
Read-onlyIdempotent

Returns turva.dev's service catalog: the agent-readiness audit, advisory, implementation, agent operations, and MCP server design, with pricing and the terms of an engagement: scope, access, dates and payment. Fixed list prices apply to the audit, advisory and implementation. Agent operations and MCP server design are on request. The catalog also lists one implementation add-on that carries a fixed price and is sold only with the audit it follows, bought with it, with its report, or after the report and before implementation starts. It also lists active security testing, an add-on to the audit that is priced by quote for each written scope, under quoted_add_ons. The audit links a published sample report in sample_url, a fictional worked example of the deliverable. Use this when a user asks what turva.dev offers, what it costs, what the terms of an engagement are, or what a delivered report looks like. For the standing rules turva.dev keeps in every engagement use get_principles instead, and for how to reach turva.dev or start an audit use get_contact. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
currencyYesISO 4217 code of every price, EUR.
servicesYesThe services with their prices.
engagementYesHow an engagement is run.
pricing_noteYesThe VAT treatment by customer type, the services quoted per engagement and the rule for the add-ons.
vat_includedYesWhether the prices include VAT. False means every price excludes VAT.
pricing_modelYesThe pricing model. fixed_list_prices means fixed list prices, apart from the services priced on request.
quoted_add_onsYesAdd-ons to a service, priced by quote for each written scope.
bundled_implementationYesImplementation add-ons that are sold only with another service.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / quoted_add_ons
      Added value: +{
      +  "description": "Add-ons to a service, priced by quote for each written scope.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "id": {
      +        "description": "Stable identifier of the add-on.",
      +        "type": "string"
      +      },
      +      "name": {
      +        "description": "The name of the add-on.",
      +        "type": "string"
      +      },
      +      "price": {
      +        "const": "on request",
      +        "description": "The price is quoted for each written scope.",
      +        "type": "string"
      +      },
      +      "requires": {
      +        "description": "The id of the service this add-on is sold with.",
      +        "type": "string"
      +      },
      +      "sold_separately": {
      +        "description": "Whether the add-on can be bought without its service. False means it cannot.",
      +        "type": "boolean"
      +      },
      +      "summary": {
      +        "description": "What the add-on covers and when it starts.",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "The page section that describes the add-on.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "name",
      +      "url",
      +      "price",
      +      "requires",
      +      "sold_separately",
      +      "summary"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "pricing_model",
      -  "pricing_note",
      -  "currency",
      -  "vat_included",
      -  "engagement",
      -  "services",
      -  "bundled_implementation"
      -]New value: +[
      +  "pricing_model",
      +  "pricing_note",
      +  "currency",
      +  "vat_included",
      +  "engagement",
      +  "services",
      +  "bundled_implementation",
      +  "quoted_add_ons"
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / bundled_implementation / items / properties / if_access_missing
      Added value: +{
      +  "description": "What happens when the required access cannot be arranged.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / bundled_implementation / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "price",
      -  "unit",
      -  "requires",
      -  "sold_separately",
      -  "summary"
      -]New value: +[
      +  "id",
      +  "name",
      +  "price",
      +  "unit",
      +  "requires",
      +  "sold_separately",
      +  "summary",
      +  "if_access_missing"
      +]
  3. Changed1 schema field changed
    • addedOutput schema / properties / services / items / properties / duration_from
      Added value: +{
      +  "description": "The event the duration counts from, where the service states one.",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / engagement / properties / notes / items / description
      Added value: +"One term of an engagement as a sentence."
  5. Changed22 schema fields changed
    • addedOutput schema / properties / bundled_implementation / description
      Added value: +"Implementation add-ons that are sold only with another service."
    • addedOutput schema / properties / bundled_implementation / items / properties / id / description
      Added value: +"Stable identifier of the add-on."
    • addedOutput schema / properties / bundled_implementation / items / properties / name / description
      Added value: +"The name of the add-on."
    • addedOutput schema / properties / bundled_implementation / items / properties / price / description
      Added value: +"Price in EUR, VAT not included."
    • addedOutput schema / properties / bundled_implementation / items / properties / sold_separately / description
      Added value: +"Whether the add-on can be bought without its service. False means it cannot."
    • addedOutput schema / properties / bundled_implementation / items / properties / summary / description
      Added value: +"What the add-on covers and when it is bought."
    • addedOutput schema / properties / bundled_implementation / items / properties / unit / description
      Added value: +"What the price covers, such as fixed."
    • addedOutput schema / properties / currency / description
      Added value: +"ISO 4217 code of every price, EUR."
    • addedOutput schema / properties / engagement / description
      Added value: +"How an engagement is run."
    • addedOutput schema / properties / engagement / properties / communication / description
      Added value: +"How an engagement is communicated, async_only for written exchange with no calls."
    • addedOutput schema / properties / engagement / properties / notes / description
      Added value: +"Terms of an engagement, one per entry, covering access, scope, dates and completion."
    • addedOutput schema / properties / pricing_model / description
      Added value: +"The pricing model. fixed_list_prices means fixed list prices, apart from the services priced on request."
    • addedOutput schema / properties / pricing_note / description
      Added value: +"The VAT treatment by customer type, the services quoted per engagement and the rule for the add-ons."
    • addedOutput schema / properties / services / description
      Added value: +"The services with their prices."
    • addedOutput schema / properties / services / items / properties / deliverable / description
      Added value: +"What the customer receives and when."
    • addedOutput schema / properties / services / items / properties / duration / description
      Added value: +"How long delivery takes, where the service states one."
    • addedOutput schema / properties / services / items / properties / id / description
      Added value: +"Stable identifier of the service."
    • addedOutput schema / properties / services / items / properties / minimum_commitment / description
      Added value: +"The shortest term the service is sold for, where one applies."
    • addedOutput schema / properties / services / items / properties / name / description
      Added value: +"The name of the service."
    • addedOutput schema / properties / services / items / properties / summary / description
      Added value: +"What the service covers and its scope."
    • addedOutput schema / properties / services / items / properties / unit / description
      Added value: +"What the price covers, such as fixed, month or day. Absent when the price is on request."
    • addedOutput schema / properties / vat_included / description
      Added value: +"Whether the prices include VAT. False means every price excludes VAT."
  6. Changed3 schema fields changed
    • 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"
      +}
  7. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark this read-only, idempotent, closed-world, and non-destructive. The description adds that the payload is static JSON compiled into the Worker, so it changes nothing and only updates on deploy; it also explains fixed-price versus on-request versus quoted add-on behavior.

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?

The first sentence front-loads purpose, and later sentences group contents, usage, alternatives, and runtime behavior. It is dense and somewhat long for a zero-parameter catalog, especially the compound add-on dependency sentence, but it avoids filler and repetition.

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?

With no params, an output schema, and rich annotations, the remaining description carries all needed context: what is listed, how pricing modes differ, what sample_url means, and which sibling to use. Nothing essential appears missing for an agent to select and call it correctly.

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?

There are no input parameters, so parameter semantics have a baseline of 4 and no missing input guidance to compensate for. The description mentions output areas like quoted_add_ons and sample_url, but that is return-content context rather than input-parameter semantics.

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?

The description uses a specific verb and resource ('Returns turva.dev's service catalog') and enumerates the catalog's main contents, including audit, advisory, implementation, operations, MCP design, pricing, and engagement terms. It also distinguishes the catalog from get_principles and get_contact by naming their purposes.

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?

It gives explicit triggers: asking what turva.dev offers, what it costs, what the engagement terms are, or what a delivered report looks like. It also names direct alternatives for standing rules and contact/start-audit needs, leaving little ambiguity about when this catalog is the right call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources