Skip to main content
Glama

agentkit__validate

Deterministic mid-task tools for AI agents: exact LLM token counting (cl100k), fit a chat message array into a context budget with a trim plan, page to markdown, repair JSON, redact secrets, encode/hash, unit and timezone maths, deadlines and cron. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: POST https://api.firstmention.uk/s/agentkit/validate

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agentkit__validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
budgetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / args
      Removed value: -{
      -  "description": "Arguments for the tool.",
      -  "type": "object"
      -}
    • addedInput schema / properties / budget
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / text
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / tool
      Removed value: -{
      -  "description": "Tool name, e.g. convert, datetime, extract, validate, repair, redact, deadlines.",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "tool"
      -]
  2. Changed6 schema fields changed
    • addedInput schema / properties / args
      Added value: +{
      +  "description": "Arguments for the tool.",
      +  "type": "object"
      +}
    • removedInput schema / properties / format
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / op
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / tool
      Added value: +{
      +  "description": "Tool name, e.g. convert, datetime, extract, validate, repair, redact, deadlines.",
      +  "type": "string"
      +}
    • removedInput schema / properties / value
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / required
      Added value: +[
      +  "tool"
      +]
  3. Changed4 schema fields changed
    • addedInput schema / properties / format
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / op
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / type
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "value"
      -]
  4. Changed4 schema fields changed
    • addedInput schema / properties / type
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / url
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / value
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "value"
      +]
  5. Changed4 schema fields changed
    • removedInput schema / properties / format
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / op
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / url
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / value
      Removed value: -{
      -  "type": "string"
      -}
  6. Changed4 schema fields changed
    • addedInput schema / properties / format
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / json
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / op
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / value
      Added value: +{
      +  "type": "string"
      +}
  7. Changed4 schema fields changed
    • removedInput schema / properties / format
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / json
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / op
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / value
      Removed value: -{
      -  "type": "string"
      -}
  8. Changed5 schema fields changed
    • removedInput schema / properties / data
      Removed value: -{}
    • removedInput schema / properties / op / enum
      Removed value: -[
      -  "format",
      -  "schema"
      -]
    • removedInput schema / properties / schema
      Removed value: -{
      -  "type": "object"
      -}
    • addedInput schema / properties / value / type
      Added value: +"string"
    • removedInput schema / required
      Removed value: -[
      -  "op"
      -]
  9. Changed8 schema fields changed
    • addedInput schema / properties / data
      Added value: +{}
    • addedInput schema / properties / format
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / from
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / op
      Added value: +{
      +  "enum": [
      +    "format",
      +    "schema"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / schema
      Added value: +{
      +  "type": "object"
      +}
    • removedInput schema / properties / to
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / value / type
      Removed value: -"string"
    • addedInput schema / required
      Added value: +[
      +  "op"
      +]
  10. Changed5 schema fields changed
    • removedInput schema / properties / chain
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / from
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / op
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / to
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / value
      Added value: +{
      +  "type": "string"
      +}
  11. Changed8 schema fields changed
    • addedInput schema / properties / chain
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / from
      Removed value: -{
      -  "description": "Source unit, e.g. km, kg, F, GB, USD, Km",
      -  "type": "string"
      -}
    • addedInput schema / properties / op
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / round
      Removed value: -{
      -  "description": "Decimal places (default 6)",
      -  "type": "integer"
      -}
    • removedInput schema / properties / to
      Removed value: -{
      -  "description": "Target unit; omit to get all equivalents in the same family",
      -  "type": "string"
      -}
    • removedInput schema / properties / value
      Removed value: -{
      -  "description": "Amount to convert",
      -  "type": "number"
      -}
    • removedInput schema / properties / values
      Removed value: -{
      -  "description": "Optional list of values instead of a single value",
      -  "items": {
      -    "type": "number"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "value",
      -  "from"
      -]
  12. First observed

TDQS

C2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It usefully discloses payment ($0.01 USDC on Base via x402 in `params._meta["x402/payment"]`) and the HTTP endpoint, but says nothing about what validation means, what is checked, whether it is read-only, or what happens on failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single run-on inventory of the entire toolkit rather than a front-loaded explanation of `validate`. Pricing and transport details are included, but the core purpose is buried or absent, so the content does not earn its space.

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 two-parameter tool with no annotations and no output schema, the description is far too thin on the operation itself. Payment and endpoint details are present, but an agent still cannot infer what the tool validates, what inputs are expected, or what result to expect.

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 must compensate for both `text` and `budget`. It does not mention either parameter or explain how they control validation, leaving their meaning entirely to the bare schema names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what `validate` actually validates. It instead advertises a broad set of sibling capabilities (token counting, chat fitting, paging, JSON repair, redaction, encoding, maths, cron) and an HTTP endpoint, leaving the tool's specific verb and resource unclear.

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 guidance on when to use this tool versus siblings such as `agentkit__repair`, `agentkit__extract`, or `agentkit__fit`. The only usage-like information is pricing and payment mechanics, which does not help an agent choose the right tool.

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