Skip to main content
Glama

turva-mcp

by dev.turva
OverviewDiscussionsAdmin

Agent-readiness score

get_agent_readiness
Read-onlyIdempotent

Returns turva.dev's own agent-readiness score from an independent public scanner (isitagentready.com), including category sub-scores, with the measurement date and a link to the scanner's start page, where a new check can be run (the link does not open the recorded reading). Use this when a user asks how turva.dev scores, whether its claims are verifiable, or what proof backs the audit service. For web-security scan results, which are a separate measurement, use get_security_evidence instead. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteYesA caveat that the scores are a point-in-time reading by an independent scanner and that the scan url opens the scanner's start page.
scansYesReadings from independent scanners, one per entry.
domainYesThe domain the reading is about.
measured_atYesDate of the reading, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedOutput schema / properties / domain / description
      Added value: +"The domain the reading is about."
    • addedOutput schema / properties / note / description
      Added value: +"A caveat that the scores are a point-in-time reading by an independent scanner and that the scan url opens the scanner's start page."
    • addedOutput schema / properties / scans / description
      Added value: +"Readings from independent scanners, one per entry."
    • addedOutput schema / properties / scans / items / properties / categories / additionalProperties / description
      Added value: +"The category score as text, out of 100."
    • addedOutput schema / properties / scans / items / properties / categories / description
      Added value: +"Sub-scores by category. Each key is a category name: discoverability, content, bot_access_control, api_auth_mcp_a2a_discovery or commerce."
    • addedOutput schema / properties / scans / items / properties / note / description
      Added value: +"Who runs the scanner and a reminder that the reading is the scanner's and can be re-run by anyone."
    • addedOutput schema / properties / scans / items / properties / provider / description
      Added value: +"The domain of the scanner that produced the reading."
    • addedOutput schema / properties / scans / items / properties / result / description
      Added value: +"The scanner's overall result as text, giving the score out of 100 and the level reached."
    • addedOutput schema / properties / scans / items / properties / url / description
      Added value: +"The scanner's start page, where a new check can be run. It does not show the recorded reading."
  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": {
+    "domain": {
+      "type": "string"
+    },
+    "measured_at": {
+      "description": "Date of the reading, YYYY-MM-DD.",
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "scans": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "categories": {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "note": {
+            "type": "string"
+          },
+          "provider": {
+            "type": "string"
+          },
+          "result": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "provider",
+          "result",
+          "note",
+          "categories",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "domain",
+    "measured_at",
+    "note",
+    "scans"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds material traits beyond them: the payload is static JSON compiled into the Worker, changes nothing, and refreshes only on deploy. It also warns that the embedded link does not open the recorded reading, a non-obvious behavioral caveat.

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?

Four sentences that are front-loaded with purpose and contents before usage and behavior. Each sentence carries distinct information, though the description is on the denser end and could be tightened slightly.

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 an output schema present and no input parameters, the description needn't explain return values. It nonetheless covers provenance, freshness cadence, the sibling alternative, and a link caveat, leaving nothing an agent needs to invoke 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?

The tool takes zero parameters, so the baseline is 4. The description still characterizes the returned payload (sub-scores, measurement date, link), though an output schema exists and already documents the response shape.

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 own agent-readiness score from an independent public scanner') and enumerates the contents: category sub-scores, measurement date, and scanner link. It clearly distinguishes itself from sibling tools by naming the distinct data source (isitagentready.com).

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?

Explicitly names the triggering conditions ('when a user asks how turva.dev scores, whether its claims are verifiable, or what proof backs the audit service') and routes the agent away from the wrong tool ('For web-security scan results... use get_security_evidence instead'). Both when-to-use and the closest alternative are covered.

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

All turva-mcp toolsInspect
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