Skip to main content
Glama

check_table_completeness

Read-only

Analyze ServiceNow table field completeness by sampling records and returning the percentage of non-empty values per field, optionally scoped by an encoded query.

Instructions

Analyze data quality and field completeness for a ServiceNow table — returns percentage of non-empty values per field

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table": "<table>",
      "fields": "<fields>"
    },
    "name": "check_table_completeness"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
queryNoOptional encoded query to scope the analysis (e.g. "active=true")
tableYesTable name to analyze (e.g. "incident", "cmdb_ci_server")
fieldsYesComma-separated field names to check (e.g. "assigned_to,priority,category")
sample_sizeNoNumber of records to sample (default 100, max 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. First observedv1.0.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful behavioral fact that results are percentages of non-empty values per field, but it says nothing about sampling caveats or result shape beyond that. With that annotation coverage, this is a moderate contribution rather than a rich one.

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?

A single compact sentence that front-loads the purpose and appends the return semantics after a dash. No filler, no restatement of the tool name.

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?

For a read-only analysis tool with a fully documented five-parameter schema and no output schema, the description covers purpose and the headline return value. It is only slightly short on sampling/latency expectations, which the async and sample_size schema entries partially imply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already documents the table, fields, query, sample_size, and async parameters with examples and defaults. The description adds no parameter-level meaning beyond what is there, so the baseline of 3 applies.

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?

Names a specific verb (analyze) and resource (data quality / field completeness of a ServiceNow table) and states the concrete output (percentage of non-empty values per field). It does not distinguish itself from the sibling analyze_data_quality, which appears to cover overlapping ground, so it falls short of a 5.

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 explicit when-to-use, when-not-to-use, or prerequisite information. The closest sibling, analyze_data_quality, is not mentioned, so an agent has no guidance on which of the two analysis tools to pick when both look applicable.

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

Deploy Server

Other Tools