Skip to main content
Glama

agentkit__datetime

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/datetime

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__datetime"
  }
}

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. Changed7 schema fields changed
    • addedInput schema / properties / args
      Added value: +{
      +  "description": "Arguments for the tool.",
      +  "type": "object"
      +}
    • removedInput schema / properties / days
      Removed value: -{
      -  "type": "number"
      -}
    • 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 / ts
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / tz
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / required
      Added value: +[
      +  "tool"
      +]
  3. Changed4 schema fields changed
    • removedInput schema / properties / date
      Removed value: -{
      -  "type": "string"
      -}
    • changedInput schema / properties / days / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / holidays
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • addedInput schema / properties / ts
      Added value: +{
      +  "type": "string"
      +}
  4. Changed6 schema fields changed
    • addedInput schema / properties / date
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / days
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / holidays
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / op
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / tz
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / url
      Removed value: -{
      -  "type": "string"
      -}
  5. Changed5 schema fields changed
    • removedInput schema / properties / amount
      Removed value: -{
      -  "type": "number"
      -}
    • removedInput schema / properties / op
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / ts
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / unit
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / url
      Added value: +{
      +  "type": "string"
      +}
  6. Changed5 schema fields changed
    • addedInput schema / properties / amount
      Added value: +{
      +  "type": "number"
      +}
    • removedInput schema / properties / json
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / op
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / ts
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / unit
      Added value: +{
      +  "type": "string"
      +}
  7. Changed4 schema fields changed
    • addedInput schema / properties / json
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / op
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / to_tz
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / ts
      Removed value: -{
      -  "type": "string"
      -}
  8. Changed8 schema fields changed
    • removedInput schema / properties / amount
      Removed value: -{
      -  "type": "number"
      -}
    • removedInput schema / properties / count
      Removed value: -{
      -  "type": "integer"
      -}
    • removedInput schema / properties / cron
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / op / enum
      Removed value: -[
      -  "now",
      -  "convert",
      -  "info",
      -  "diff",
      -  "add",
      -  "cron"
      -]
    • removedInput schema / properties / ts2
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / tz
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / unit
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "op"
      -]
  9. Changed13 schema fields changed
    • addedInput schema / properties / amount
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / count
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / cron
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / from
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / op
      Added value: +{
      +  "enum": [
      +    "now",
      +    "convert",
      +    "info",
      +    "diff",
      +    "add",
      +    "cron"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / to
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / to_tz
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / ts
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / ts2
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / tz
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / unit
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / value
      Removed value: -{
      -  "type": "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

D1.9/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 behavioral burden, and it does add genuinely useful context: a $0.01 USDC charge on Base (eip155:8453), x402 payment placed in params._meta["x402/payment"], and the POST endpoint. However, it discloses nothing about what the operation actually does, what it returns, whether it is read-only, or failure modes — so the agent knows the price but not the behavior.

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?

It is a single dense run-on sentence cataloguing roughly ten unrelated capabilities, front-loaded with the suite pitch instead of the tool's own function. The pricing and endpoint trailer is compact, but the bulk of the text does not earn its place for this specific tool.

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 definition should say what the call computes, what 'text' and 'budget' mean, and what comes back. Instead it describes the whole product family, leaving the agent unable to invoke this endpoint with confidence despite knowing its price and URL.

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

Parameters1/5

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

Schema coverage is 0% for two parameters ('text' string, 'budget' number) and the description never mentions either one. Worse, those parameter names are semantically unrelated to the tool's apparent datetime domain, and the blurb's only 'budget' reference belongs to the fit/context-trimming tool, which actively misleads. Nothing is added beyond the bare schema.

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 text is a suite-level catalog blurb ('exact LLM token counting, fit a chat message array..., page to markdown, repair JSON, redact secrets, encode/hash, unit and timezone maths, deadlines and cron') rather than a statement of what agentkit__datetime does. The only fragment plausibly covering this tool ('unit and timezone maths, deadlines and cron') is bundled with the separate agentkit__deadlines sibling, so the agent cannot tell which capability belongs here. It never gives a specific verb+resource for this tool.

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 when-to-use or when-not-to-use guidance for this tool. The description enumerates many capabilities without saying which one this endpoint performs, and gives no routing rule distinguishing it from siblings like agentkit__deadlines or agentkit__convert. The only actionable instruction is the HTTP transport/payment note, which is not usage guidance.

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