Skip to main content
Glama

Inspect data coverage

get_data_quality
Read-onlyIdempotent

Snapshot coverage and missing metadata, unresolved loaded-authority links, semantic-neighbour coverage and sanitized refresh status. Missing catalogue metadata is not evidence of real-world absence.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countsYes
missingYes
refreshYes
fetched_atYes
snapshot_idYes
schema_versionYes
literal_entitiesYes
semantic_neighboursYes
unresolved_entitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / counts / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / missing / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / refresh / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / semantic_neighbours / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "propertyNames": {
      -      "type": "string"
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / semantic_neighbours
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {},
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "snapshot_id",
      -  "fetched_at",
      -  "schema_version",
      -  "counts",
      -  "missing",
      -  "unresolved_entities",
      -  "literal_entities",
      -  "refresh"
      -]New value: +[
      +  "snapshot_id",
      +  "fetched_at",
      +  "schema_version",
      +  "counts",
      +  "missing",
      +  "unresolved_entities",
      +  "literal_entities",
      +  "refresh",
      +  "semantic_neighbours"
      +]
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful interpretive context by labeling refresh status as sanitized and warning that missing catalogue metadata is not evidence of real-world absence, but it says nothing about output shape, granularity, or limits.

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?

Two compact sentences with no wasted prose, and the important caveat is preserved at the end. The first sentence is a dense list of nouns rather than a clear declarative statement, which slightly hurts readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no inputs, rich annotations, and an output schema, so the description does not need to explain return structure. It adequately communicates the inspection scope and the key interpretive caveat, though it could be clearer about what 'sanitized refresh status' actually means.

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 there is no parameter semantics burden on the description. Baseline 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific dimensions being inspected: coverage, missing metadata, unresolved authority links, semantic-neighbour coverage, and refresh status. This is clearly a data-quality inspection tool, but the fragmentary noun phrase has no explicit verb and does not differentiate it from any sibling by name.

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

Usage Guidelines2/5

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

There is no guidance on when to call this tool, what question it answers, or which sibling to use instead. The caveat about missing catalogue metadata is an interpretive warning, not usage direction.

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.