Skip to main content
Glama

Web-security scan evidence

get_security_evidence
Read-onlyIdempotent

Returns the latest public web-security scan results for turva.dev's own domain (Hardenize, Internet.nl site and mail), each with its scan date. Use this when a user asks about turva.dev's own security posture or wants evidence beyond agent-readiness scores. For the agent-readiness score itself, which is a separate measurement, use get_agent_readiness instead. 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_security_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteYesWhy turva.dev publishes the scan results of its own domain.
scansYesWeb-security scan results, one per provider and test.
domainYesThe domain the scans are about.
measured_atYesDate of the Internet.nl readings, YYYY-MM-DD. Every entry in scans carries its own measured_at, which is the date of that reading.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / measured_at / description
      Previous value: -"Date of the scans, YYYY-MM-DD."New value: +"Date of the Internet.nl readings, YYYY-MM-DD. Every entry in scans carries its own measured_at, which is the date of that reading."
  2. Changed2 schema fields changed
    • changedOutput schema / properties / scans / items / properties / measured_at / description
      Previous value: -"Date of this reading, YYYY-MM-DD, on a reading that carries its own date. It can equal the top-level date."New value: +"Date of this reading, YYYY-MM-DD. It can equal the top-level date."
    • changedOutput schema / properties / scans / items / required
      Previous value: -[
      -  "provider",
      -  "url"
      -]New value: +[
      +  "provider",
      +  "measured_at",
      +  "url"
      +]
  3. Changed10 schema fields changed
    • addedOutput schema / properties / domain / description
      Added value: +"The domain the scans are about."
    • addedOutput schema / properties / note / description
      Added value: +"Why turva.dev publishes the scan results of its own domain."
    • addedOutput schema / properties / scans / description
      Added value: +"Web-security scan results, one per provider and test."
    • changedOutput schema / properties / scans / items / properties / measured_at / description
      Previous value: -"Date of this reading, YYYY-MM-DD, when it differs from the top-level date."New value: +"Date of this reading, YYYY-MM-DD, on a reading that carries its own date. It can equal the top-level date."
    • addedOutput schema / properties / scans / items / properties / note / description
      Added value: +"What passed in full and where the points were lost. Absent when the provider adds no note."
    • addedOutput schema / properties / scans / items / properties / provider / description
      Added value: +"The name of the scan provider."
    • addedOutput schema / properties / scans / items / properties / result / description
      Added value: +"The overall result as text, for a provider that reports passed categories instead of a number. Absent when a numeric score is given."
    • addedOutput schema / properties / scans / items / properties / scale / description
      Added value: +"The range of the score, written as low-high. Absent when there is no numeric score."
    • addedOutput schema / properties / scans / items / properties / score / description
      Added value: +"The numeric score, on the range given in scale. Absent when the provider reports a text result."
    • addedOutput schema / properties / scans / items / properties / url / description
      Added value: +"The provider's public report page for the domain."
  4. Changed2 schema fields changed
    • addedOutput schema / properties / scans / items / properties / measured_at
      Added value: +{
      +  "description": "Date of this reading, YYYY-MM-DD, when it differs from the top-level date.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / scans / items / required
      Previous value: -[
      -  "provider"
      -]New value: +[
      +  "provider",
      +  "url"
      +]
  5. Changed1 schema field changed
    • changedOutput schema / properties / scans / items / required
      Previous value: -[
      -  "provider",
      -  "url"
      -]New value: +[
      +  "provider"
      +]
  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": {
      +    "domain": {
      +      "type": "string"
      +    },
      +    "measured_at": {
      +      "description": "Date of the scans, YYYY-MM-DD.",
      +      "type": "string"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "scans": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "note": {
      +            "type": "string"
      +          },
      +          "provider": {
      +            "type": "string"
      +          },
      +          "result": {
      +            "type": "string"
      +          },
      +          "scale": {
      +            "type": "string"
      +          },
      +          "score": {
      +            "type": "number"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "provider",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "domain",
      +    "measured_at",
      +    "scans",
      +    "note"
      +  ],
      +  "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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes further and discloses data provenance and freshness semantics that annotations cannot express: the JSON is compiled into the Worker and therefore only refreshes on deploy, meaning results may be stale relative to the live domain. That is exactly the extra context an agent needs before quoting the evidence as current.

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?

Three sentences, front-loaded with what is returned, then when to use it, then behavioral notes. There is minor redundancy in 'Read-only ... so it changes nothing', which restates the readOnlyHint before delivering the genuinely new point about deploy-time updates.

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 read tool with an output schema and full annotation coverage, the description supplies everything remaining: source systems, scope, trigger conditions, the sibling to use instead, and staleness behavior. Nothing an agent needs in order 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 there is no parameter meaning to add; the baseline for a 0-param tool is 4. The description does not invent arguments and correctly presents the call as argument-free.

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 the latest public web-security scan results') and pins the scope to turva.dev's own domain with the named sources (Hardenize, Internet.nl site and mail). It explicitly separates itself from the agent-readiness measurement, so an agent can distinguish it from the sibling without opening the 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 both a positive trigger ('when a user asks about turva.dev's own security posture or wants evidence beyond agent-readiness scores') and a routing rule to the alternative ('For the agent-readiness score itself ... use get_agent_readiness instead'). Nothing about tool selection 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources