Skip to main content
Glama

Engagement principles

get_principles
Read-onlyIdempotent

Returns turva.dev's four engagement principles, each with its reason: async-only, least access, each fix checked with a scanner or a direct test, and open and verifiable. Use this when a user asks what turva.dev stands by or why it works the way it does, for example why there are no calls. For the terms of an engagement, its scope, access, dates, payment and prices, use get_services instead, and for how to start 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_principles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
modelYesThe service model the principles belong to, agent_readiness_audit for the agent-readiness audit.
rulesYesThe principles an engagement follows, one per entry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / model / description
      Added value: +"The service model the principles belong to, agent_readiness_audit for the agent-readiness audit."
    • addedOutput schema / properties / rules / description
      Added value: +"The principles an engagement follows, one per entry."
    • addedOutput schema / properties / rules / items / properties / id / description
      Added value: +"Stable identifier of the principle."
    • addedOutput schema / properties / rules / items / properties / rationale / description
      Added value: +"What the principle means in practice and why it holds."
    • addedOutput schema / properties / rules / items / properties / title / description
      Added value: +"The principle in a short phrase."
  2. 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": {
      +    "model": {
      +      "type": "string"
      +    },
      +    "rules": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "id": {
      +            "type": "string"
      +          },
      +          "rationale": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "title",
      +          "rationale"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "model",
      +    "rules"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, but the description adds meaningful context beyond them: the JSON is static and compiled into the Worker, so nothing changes and updates occur only on deploy. It does not need to explain the return shape because an output schema exists.

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?

It is front-loaded with the content and reason, then usage, then sibling routing, then execution traits; every sentence adds distinct value with no filler.

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 zero-parameter, static, read-only tool with rich annotations and an output schema, the description covers purpose, routing, and deployment semantics completely; nothing needed to call it correctly is missing.

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 has zero parameters, so the baseline is 4; the description correctly requires no parameter explanation and avoids inventing any.

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 names the concrete resource (turva.dev's four engagement principles) and enumerates the four principles, so the agent knows exactly what is returned and can distinguish it from get_services or get_contact.

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 states explicitly when to use it (user asks what turva.dev stands by or why it works as it does), gives an example, and routes the agent to get_services for engagement terms and get_contact for how to start.

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