Skip to main content
Glama

veritas-8183-agent-notary-witness

audit_rag_embeddings_escrow

Idempotent

[Private] Are these RAG chunks and embeddings usable and clean? Checks dimensions, norms, duplicates and hidden prompt injection. Example: expectedDimension=4, minChunks=5.

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": {
      "chunks": "<chunks>"
    },
    "name": "audit_rag_embeddings_escrow"
  }
}

Input Schema

NameRequiredDescriptionDefault
chunksYesArray of RAG objects containing text and numeric embedding arrays.
minChunksNoMinimum required number of valid knowledge chunks.
expectedDimensionNoExpected vector length for every embedding.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / chunks / description
      Added value: +"Array of RAG objects containing text and numeric embedding arrays."
    • addedInput schema / properties / chunks / items
      Added value: +{
      +  "type": "object"
      +}
    • addedInput schema / properties / expectedDimension / description
      Added value: +"Expected vector length for every embedding."
    • addedInput schema / properties / minChunks / description
      Added value: +"Minimum required number of valid knowledge chunks."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare idempotent, non-destructive, non-open-world, and not read-only behavior. The description usefully adds the specific validation categories, but it does not explain what state changes occur despite readOnlyHint=false or what happens when the audit fails.

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?

The description is short and front-loaded: the question establishes purpose, the second sentence lists the checks, and the third gives a compact parameter example. There is no unnecessary wording.

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

Completeness3/5

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

For a three-parameter audit tool with no output schema, the definition covers purpose and validation scope adequately against the supplied annotations. However, it omits return-value expectations, failure semantics, and any side-effect disclosure that would matter given readOnlyHint=false.

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%, so the baseline is 3 even without additional parameter detail in the description. The example values (expectedDimension=4, minChunks=5) add a little practical context, but no constraints beyond what the schema already documents.

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 states a specific resource (RAG chunks and embeddings) and concrete checks (dimensions, norms, duplicates, hidden prompt injection), so the audit purpose is clear. It does not explicitly differentiate itself from sibling audit_*_escrow tools, but the RAG-specific scope makes it distinguishable.

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

Usage Guidelines3/5

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

Usage is implied by the question and the listed validation checks, but there is no explicit when-to-use guidance, no exclusions, and no alternative tools named. The example clarifies expected parameters but does not explain when this audit is preferable to other audits.

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.