Skip to main content
Glama
Sign In

Kamy

by dev.kamy
OverviewDiscussionsAdmin

Validate payload

validate_payload
Read-only

Dry-run a render payload against a template's schema WITHOUT producing a PDF or using quota. Returns per-field self-healing errors (expected type, value received, allowed values, an example) so you can fix the data before render_pdf. Requires a Kamy API key.

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": {
      "template": "<template>",
      "data": "<data>"
    },
    "name": "validate_payload"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe data payload to validate against the template schema.
templateYesTemplate slug (e.g. 'invoice') or template UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly, non-destructive), the description adds valuable behavioral details: it does not generate a PDF or use quota, requires a Kamy API key, and returns self-healing per-field errors including expected type, value received, allowed values, and an example. This exceeds the annotation baseline and provides significant operational context.

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 concise, front-loads the primary action, and every clause adds value—mentioning the dry-run nature, the return error format, the parallel to render_pdf, and the auth requirement. Nothing is redundant or wasted.

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

Completeness5/5

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

Given the tool's moderate complexity, the description covers the purpose, usage timing, return behavior, and auth requirement. Since there is no output schema, the description sufficiently explains what the tool returns (self-healing errors). It leaves minimal gaps for an agent to misuse the tool.

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%, with both parameters already described ('data' as the payload and 'template' as slug or UUID). The description does not add extra meaning beyond the schema, so it stays at the baseline of 3.

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?

The description clearly states the tool validates a payload against a template schema, with a specific verb ('Dry-run'), and distinguishes itself from render_pdf by explicitly noting it does NOT produce a PDF or consume quota. This makes the purpose unambiguous and differentiates it from sibling tools.

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?

The description gives clear context by saying it lets you 'fix the data before render_pdf,' implying it should be used prior to rendering. However, it does not explicitly mention when not to use it or name alternative tools like get_template_schema, so it falls short of a full 5.

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

All Kamy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources