Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

agentkit__mcp

MCP-style tool dispatch endpoint. 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/mcp

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

Input Schema

NameRequiredDescriptionDefault
argsNo
toolNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / args
      Added value: +{
+  "properties": {},
+  "type": "object"
+}
    • removedInput schema / properties / id
      Removed value: -{
-  "type": "number"
-}
    • removedInput schema / properties / jsonrpc
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / method
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / params
      Removed value: -{
-  "properties": {
-    "arguments": {
-      "properties": {
-        "json": {
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "name": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / tool
      Added value: +{
+  "type": "string"
+}
  2. Changed5 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
+  "type": "number"
+}
    • addedInput schema / properties / jsonrpc
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / method
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / params
      Added value: +{
+  "properties": {
+    "arguments": {
+      "properties": {
+        "json": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / url
      Removed value: -{
-  "type": "string"
-}
  3. Added

TDQS

C2.4/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 does usefully disclose cost ($0.01 USDC on Base) and the x402 payment flow, but omits what happens on dispatch (read vs. write, side effects), what is returned, and how failures or unpaid calls behave. It also points to params._meta["x402/payment"], a field that does not appear in the input schema, leaving the actual payment mechanics unclear.

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?

Two short sentences with the purpose front-loaded and no filler. The pricing and endpoint details are compact, though the brevity comes at the cost of the missing semantics noted elsewhere.

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 generic dispatch endpoint with zero schema descriptions, no annotations, and no output schema, the description should explain which tools are dispatchable and the expected args/return shape. None of that is present, so an agent cannot construct a correct call from this definition alone.

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 coverage is 0% and the description adds no meaning for either parameter: it never explains that "tool" selects the target tool or what shape "args" must take. Worse, it references a _meta parameter that the schema does not define, which actively misleads rather than compensating for the coverage gap.

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

Purpose3/5

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

"MCP-style tool dispatch endpoint" names a category of behavior, but it never says what is being dispatched (which tools, which service, what a call does). An agent cannot distinguish this from the many agentkit__* siblings or tell whether it is a meta-proxy or a concrete operation.

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 mention of alternatives among the ~150 sibling tools. The only selection signal offered is price and payment method, which tells an agent what it costs but not when it should prefer this dispatcher over agentkit__batch or any specific tool.

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

All automaton 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