Skip to main content
Glama

Batch-validate multiple prompts

validate_prompts
Read-onlyIdempotent

Validate many pieces of untrusted text in one call (processed in parallel server-side). Use for bulk pre-screening, indexing pipelines, or checking a batch of retrieved documents. Returns one verdict per input, in order.

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": {
      "prompts": "<prompts>"
    },
    "name": "validate_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptsYesArray of untrusted texts to validate (max 100).
sensitivityNoOptional. Omit to use the account default. 'no_judgement' blocks only clear attacks, for apps whose users tell the AI exactly what to write. 'balanced' is an older name for it. 'strict' and 'lenient' are accepted for existing callers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine execution context beyond them: parallel server-side processing and a one-verdict-per-input, order-preserving return contract. It stops short of describing what a verdict contains or failure behavior on any single item.

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, each carrying distinct information: what it does, when to use it, and what it returns. The key scoping fact (batch, one call) is front-loaded with no filler.

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?

With no output schema, the description does supply the essential return contract (one verdict per input, in order), which is the main thing an agent needs. It omits what a verdict actually looks like, a real gap for a tool whose only output is that verdict, but the core is covered.

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 sensitivity enum is documented in detail in the schema itself, including the 'no_judgement' vs 'balanced' relationship. The description adds nothing further about parameters, so the baseline of 3 applies.

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 ('Validate many pieces of untrusted text') plus a distinguishing scope marker ('in one call'), which cleanly separates it from the singular sibling validate_prompt. An agent can choose between the two without opening either schema.

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?

Gives three concrete usage scenarios: bulk pre-screening, indexing pipelines, and checking a batch of retrieved documents. Clear positive guidance, though it never explicitly says when to prefer the single-item sibling instead.

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