automaton

agentkit__chain

Resolve chain id to CAIP-2 and metadata. 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/chain

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

Input Schema

Name	Required	Description	Default
`op`	No
`chain`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026
- addedInput schema / properties / chain
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / op
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / q
```
Removed value: -{
-  "type": "string"
-}
```
Changed2 schema fields changedNov 3, 2026
- addedInput schema / properties / q
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / url
```
Removed value: -{
-  "type": "string"
-}
```
Changed2 schema fields changedNov 3, 2026
- removedInput schema / properties / chain
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```
Changed2 schema fields changedNov 3, 2026
- addedInput schema / properties / chain
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / json
```
Removed value: -{
-  "type": "string"
-}
```
Changed3 schema fields changedNov 2, 2026
- removedInput schema / properties / chain
```
Removed value: -{
-  "type": "number"
-}
```
- addedInput schema / properties / json
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / op
```
Removed value: -{
-  "type": "string"
-}
```
Changed6 schema fields changedNov 2, 2026
- removedInput schema / properties / caip
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / chain / type
```
Added value: +"number"
```
- removedInput schema / properties / namespace
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / op / enum
```
Removed value: -[
-  "info",
-  "list",
-  "validate",
-  "equal"
-]
```
- removedInput schema / properties / testnet
```
Removed value: -{
-  "type": "boolean"
-}
```
- removedInput schema / required
```
Removed value: -[
-  "op"
-]
```

Changed9 schema fields changedNov 2, 2026

addedInput schema / properties / caip
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / chain
```
Added value: +{}
```

removedInput schema / properties / from

Removed value: -{
-  "type": "string"
-}

addedInput schema / properties / namespace
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / op

Added value: +{
+  "enum": [
+    "info",
+    "list",
+    "validate",
+    "equal"
+  ],
+  "type": "string"
+}

addedInput schema / properties / testnet
```
Added value: +{
+  "type": "boolean"
+}
```

removedInput schema / properties / to

Removed value: -{
-  "type": "string"
-}

removedInput schema / properties / value

Removed value: -{
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "op"
+]
```

Changed5 schema fields changedOct 31, 2026
- 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"
+}
```
AddedOct 30, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the single most operationally critical fact: this is a paid call ($0.01 USDC on eip155:8453) requiring an x402 payment in params._meta['x402/payment'], plus the HTTP transport. It omits error behavior (unknown chain id), whether the call is a pure read, and what 'metadata' actually contains, so an agent still cannot predict the outcome of a successful call.

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

Conciseness4/5

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

Three short, front-loaded lines: purpose first, then price/payment mechanics, then transport. No filler, though the raw endpoint URL is arguably redundant with the tool binding.

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 two-parameter tool with no annotations, no output schema, and zero schema coverage, the description covers payment mechanics well but leaves the 'op' parameter and the returned 'metadata' shape undefined. It is adequate to know what the tool is, not quite enough to invoke it confidently the first time.

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% across two parameters, and the description only obliquely explains 'chain' as a chain id. The 'op' parameter receives no explanation anywhere, so an agent cannot know what operation selector is expected or what values are valid.

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 gives a specific verb and resource: 'Resolve chain id to CAIP-2 and metadata', so the agent knows exactly what transformation is performed. It does not, however, distinguish itself from plausible siblings like chainread__network or agentkit__convert, which also look like identifier/network resolution tools.

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 call this versus agentkit__convert or chainread__network, and no stated prerequisites beyond the payment note. The agent must infer the use case entirely from the one-line purpose.

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

All automaton tools Inspect

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

Need Help?