Skip to main content
Glama

MCP Verification Gate: check an MCP server or an A2A agent before you connect or delegate

Get the conformance conditions

get_conditions
Read-onlyIdempotent

Return the five conditions this gate measures, what it explicitly does not verify, and the tier definitions. Takes no arguments and returns identical output every time. Read this before running a check so you know what a verdict does and does not claim.

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_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
gateNoName of this gate.
tiersNoThe status words a verdict can carry and what each one means.
lookupNoHow to read the register for one endpoint before connecting (GET /register/lookup).
consentNoWhen this gate calls a tool on a checked server, and what counts as the owner's consent.
versionNoVersion of the gate code that produced this document.
operatorNoWho operates this gate.
red_teamNoThe adversarial test suite this gate is run against, with its scores by version.
conditionsNoThe measured conditions, keyed by condition id, each with what is measured and how.
mcp_clientNoHow this gate calls an MCP endpoint (Accept, initialize params, versions, session, event stream limits) since 0.4.24, and the correction for 0.4.22 and earlier.
gate_commitNoGit commit of the deployed gate, or a sentence saying the deployment did not pin one.
reachabilityNoHow an answer from the server is told apart from a failure to reach it (pending versus held).
record_bytesNoWhere the exact bytes that record_sha256 hashes are served, and since when.
self_appliedNoStatement that this gate is measured under its own conditions.
number_safetyNoHow numbers in a verdict are kept recomputable across JSON implementations.
instant_coordinateNoHow the time of a scheduled measurement and the measured tool are derived rather than chosen.
well_known_consentNoThe consent file an origin can publish, its path and its fields.
what_this_verifiesNoThe claims a verdict from this gate supports, as sentences.
also_measured_no_verdictNoMeasurements that are disclosed and never change a verdict.
what_this_does_not_verifyNoWhat a verdict from this gate never supports, as sentences.
establishes_and_does_not_establishNoWhat a verdict establishes and what it does not, as two lists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / mcp_client
      Added value: +{
      +  "description": "How this gate calls an MCP endpoint (Accept, initialize params, versions, session, event stream limits) since 0.4.24, and the correction for 0.4.22 and earlier.",
      +  "type": "object"
      +}
  2. Changed22 schema fields changed
    • addedOutput schema / properties / also_measured_no_verdict
      Added value: +{
      +  "description": "Measurements that are disclosed and never change a verdict.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / conditions / description
      Added value: +"The measured conditions, keyed by condition id, each with what is measured and how."
    • changedOutput schema / properties / conditions / type
      Previous value: -[
      -  "array",
      -  "object"
      -]New value: +"object"
    • addedOutput schema / properties / consent
      Added value: +{
      +  "description": "When this gate calls a tool on a checked server, and what counts as the owner's consent.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / establishes_and_does_not_establish
      Added value: +{
      +  "description": "What a verdict establishes and what it does not, as two lists.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / gate
      Added value: +{
      +  "description": "Name of this gate.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / gate_commit
      Added value: +{
      +  "description": "Git commit of the deployed gate, or a sentence saying the deployment did not pin one.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / instant_coordinate
      Added value: +{
      +  "description": "How the time of a scheduled measurement and the measured tool are derived rather than chosen.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / lookup
      Added value: +{
      +  "description": "How to read the register for one endpoint before connecting (GET /register/lookup).",
      +  "type": "object"
      +}
    • removedOutput schema / properties / not_verified
      Removed value: -{
      -  "type": [
      -    "array",
      -    "object",
      -    "string"
      -  ]
      -}
    • addedOutput schema / properties / number_safety
      Added value: +{
      +  "description": "How numbers in a verdict are kept recomputable across JSON implementations.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / operator
      Added value: +{
      +  "description": "Who operates this gate.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / reachability
      Added value: +{
      +  "description": "How an answer from the server is told apart from a failure to reach it (pending versus held).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / record_bytes
      Added value: +{
      +  "description": "Where the exact bytes that record_sha256 hashes are served, and since when.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / red_team
      Added value: +{
      +  "description": "The adversarial test suite this gate is run against, with its scores by version.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / self_applied
      Added value: +{
      +  "description": "Statement that this gate is measured under its own conditions.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / tiers / description
      Added value: +"The status words a verdict can carry and what each one means."
    • changedOutput schema / properties / tiers / type
      Previous value: -[
      -  "array",
      -  "object"
      -]New value: +"object"
    • addedOutput schema / properties / version
      Added value: +{
      +  "description": "Version of the gate code that produced this document.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / well_known_consent
      Added value: +{
      +  "description": "The consent file an origin can publish, its path and its fields.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / what_this_does_not_verify
      Added value: +{
      +  "description": "What a verdict from this gate never supports, as sentences.",
      +  "type": "array"
      +}
    • addedOutput schema / properties / what_this_verifies
      Added value: +{
      +  "description": "The claims a verdict from this gate supports, as sentences.",
      +  "type": "array"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Deterministic. Takes no arguments, looks nothing up, and returns the same document every time. It therefore declares no read-state field, and a structural probe will score it as unable to hold the difference between a failed read and an empty one. That score is correct and is left standing: this tool has no read to fail. Adding a state field it can never use would make the number look better and mean less.",
      +  "properties": {
      +    "conditions": {
      +      "type": [
      +        "array",
      +        "object"
      +      ]
      +    },
      +    "not_verified": {
      +      "type": [
      +        "array",
      +        "object",
      +        "string"
      +      ]
      +    },
      +    "tiers": {
      +      "type": [
      +        "array",
      +        "object"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  4. First observed

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new facts: zero arguments, identical output every time, and the specific content boundaries (it documents what the gate does NOT verify), which is material to interpreting verdicts. It does not describe size or format of the returned content, but the output schema covers that.

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?

Three short sentences, front-loaded with the return payload, then the invariants, then the call-order advice. Nothing is redundant and no sentence could be dropped without losing information.

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-argument read tool with annotations and an output schema, this description supplies everything missing from structured fields: the static-output guarantee and the interpretive caution about what a verdict does and does not claim. No behavioral gap remains for an agent deciding whether to call it first.

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 description's explicit 'takes no arguments' is sufficient and matches the empty schema with additionalProperties=false. Baseline 4 applies for a parameterless tool; there is no additional semantic depth to add.

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 ('Return the five conditions this gate measures') and enumerates the payload: conditions, non-verified items, and tier definitions. An agent can distinguish this from check_conformance or verify_verdict purely from the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Read this before running a check' gives a clear ordering recommendation relative to the check_conformance sibling, which is exactly the context an agent needs. It stops short of saying when not to call it (e.g., if results are already cached in context) or naming the sibling tools explicitly, so it is strong but not exhaustive.

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.