Skip to main content
Glama

agentkit__convert

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

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

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 / from
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / to
      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": "number"
      -}
    • addedInput schema / required
      Added value: +[
      +  "tool"
      +]
  3. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
      -  "value",
      -  "from",
      -  "to"
      -]
  4. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[
      +  "value",
      +  "from",
      +  "to"
      +]
  5. Changed1 schema field changed
    • removedInput schema / properties / round
      Removed value: -{
      -  "type": "number"
      -}
  6. Changed5 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / json
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / round
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / value
      Added value: +{
      +  "type": "number"
      +}
  7. Changed4 schema fields changed
    • removedInput schema / properties / from
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / json
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / to
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / value
      Removed value: -{
      -  "type": "number"
      -}
  8. Changed3 schema fields changed
    • removedInput schema / properties / round
      Removed value: -{
      -  "type": "integer"
      -}
    • removedInput schema / properties / values
      Removed value: -{
      -  "items": {
      -    "type": "number"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "value"
      -]
  9. Changed4 schema fields changed
    • addedInput schema / properties / round
      Added value: +{
      +  "type": "integer"
      +}
    • changedInput schema / properties / value / type
      Previous value: -"string"New value: +"number"
    • addedInput schema / properties / values
      Added value: +{
      +  "items": {
      +    "type": "number"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / required
      Added value: +[
      +  "value"
      +]
  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.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add genuinely useful non-schema facts — $0.01 per call in USDC on Base (eip155:8453), payment via x402 in params._meta['x402/payment'], and the HTTP endpoint — but says nothing about what an invocation actually does, whether operations are pure reads, how failures surface, or what the result looks like.

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 definition is a single run-on enumeration of unrelated capabilities followed by billing and endpoint details. It is not front-loaded with this tool's actual function, and the capability list does not earn its place because none of it is actionable against the given schema.

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

Completeness1/5

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

With no output schema, no annotations, two undocumented optional parameters, and an advertised multi-operation surface lacking any operation selector, the definition is materially inadequate for correct invocation. Payment and endpoint information is included, but the core contract is missing.

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 both parameters, so the description must define them. It never mentions 'text' or 'budget' as inputs, and more seriously there is no parameter that could select between token counting, JSON repair, redaction and the other advertised operations. An agent cannot construct a valid call from this text.

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 names many concrete verbs and resources (token counting, context-budget fitting, page-to-markdown, JSON repair, redaction, encode/hash, timezone maths, cron), but never says which of these this specific tool performs or how an agent selects among them. Read against a schema containing only 'text' and 'budget', it reads as a catalog of an entire service rather than a statement of this endpoint's job.

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 guidance and no routing to alternatives, even though sibling tools named tokens, fit, fetchmd, repair, redact, encode, datetime and deadlines appear to cover the same listed capabilities individually. The only operational guidance is pricing and transport details, not selection criteria.

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