Skip to main content
Glama

Basic email field shape

bpj_dq_email_shape
Read-onlyIdempotent

Screen for a single at-sign, a dotted domain and no whitespace in an email address.

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": {
      "rows": "<rows>",
      "column": "<column>"
    },
    "name": "bpj_dq_email_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so safety behavior is covered. The description adds the screening predicate but omits what the check returns, how null/empty values are handled, and whether multiple violations are reported; it remains thin for a check with no output schema.

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, front-loaded sentence with no filler. It is appropriately sized for the stated check, though conciseness does not make up for the missing operational detail.

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

Completeness2/5

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

For a read-only data-quality check, the description gives the predicate but not the input contract or result shape. With no output schema and 0% parameter description coverage, an agent lacks enough detail about how rows/column are consumed and what a screening result contains.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to explain rows and column, but it never mentions either parameter. At most, 'in an email address' hints that the column holds email addresses; it does not explain that rows is a JSON record array or how column selects the field to test.

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 gives a specific verb ('Screen for') and a concrete predicate: one at-sign, a dotted domain, and no whitespace in an email address. It does not explicitly distinguish this from sibling checks like bpj_dq_web_addresses or bpj_dq_identifier_shape, so it stops short of 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 or when-not-to-use guidance and no alternative named. The only usage signal is implied by the screening purpose; an agent must infer that this is a data-quality check on a column of email addresses.

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.