Agent Decision & Evidence Tools (MCP + x402)

AgentLLM Micro inference

agentllm_micro

Read-only

OpenAI-compatible classification, extraction, routing and short summaries for exactly 0.003 USDC per call. Validate the exact JSON for free first; no account or API key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`prompt`	Yes
`system`	No
`max_tokens`	No

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`tool`	No
`error`	No
`model`	No
`usage`	No
`object`	No
`charged`	No	When present on an error, false means the failed result is uncharged.
`choices`	No
`created`	No
`message`	No
`missing`	No
`receipt`	No
`settled`	No	When present on an error, false means no settlement occurred.
`unknown`	No
`accepted`	No
`retryable`	No
`error_code`	No
`extensions`	No
`status_code`	No
`did_you_mean`	No
`x402_service`	No
`missing_checks`	No
`partial_evidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 6, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / max_tokens / maximum
```
Added value: +300
```
addedInput schema / properties / max_tokens / minimum
```
Added value: +1
```
removedInput schema / properties / max_tokens / title
```
Removed value: -"Max Tokens"
```
addedInput schema / properties / prompt / maxLength
```
Added value: +6000
```
addedInput schema / properties / prompt / minLength
```
Added value: +1
```
removedInput schema / properties / prompt / title
```
Removed value: -"Prompt"
```
addedInput schema / properties / system / maxLength
```
Added value: +2000
```
removedInput schema / properties / system / title
```
Removed value: -"System"
```

removedInput schema / title

Removed value: -"agentllm_micro_toolArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "id",
+        "object",
+        "created",
+        "model",
+        "choices",
+        "usage",
+        "x402_service",
+        "receipt",
+        "extensions"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "description": "Structured result contract for agentllm_micro. A success satisfies the documented success branch. A domain or tool error includes error and is not a successful settlement; unpaid x402 requirements are carried by the transport wrapper.",
+  "properties": {
+    "accepted": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "charged": {
+      "description": "When present on an error, false means the failed result is uncharged.",
+      "type": "boolean"
+    },
+    "choices": {
+      "items": {},
+      "type": "array"
+    },
+    "created": {
+      "type": "integer"
+    },
+    "did_you_mean": {
+      "additionalProperties": true,
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "error": {
+      "oneOf": [
+        {
+          "type": "string"
+        },
+        {
+          "additionalProperties": true,
+          "properties": {
+            "code": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "message": {
+              "type": "string"
+            },
+            "param": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "message"
+          ],
+          "type": "object"
+        }
+      ]
+    },
+    "error_code": {
+      "type": "string"
+    },
+    "extensions": {
+      "additionalProperties": true,
+      "properties": {
+        "delivery-receipt": {
+          "additionalProperties": true,
+          "properties": {
+            "how_to_verify": {
+              "type": "string"
+            },
+            "issued_at": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "issuer": {
+              "type": "string"
+            },
+            "issuer_key": {
+              "type": "string"
+            },
+            "key_id": {
+              "type": "string"
+            },
+            "result_hash": {
+              "type": "string"
+            },
+            "service": {
+              "type": "string"
+            },
+            "signature": {
+              "type": "string"
+            },
+            "signed_message": {
+              "type": "string"
+            },
+            "standard": {
+              "const": "eucompliance-receipt/2",
+              "type": "string"
+            },
+            "subject": {
+              "type": "string"
+            },
+            "valid_until": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "verify_url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "standard",
+            "service",
+            "subject",
+            "result_hash",
+            "issued_at",
+            "valid_until",
+            "issuer",
+            "issuer_key",
+            "key_id",
+            "verify_url",
+            "how_to_verify",
+            "signature",
+            "signed_message"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "delivery-receipt"
+      ],
+      "type": "object"
+    },
+    "id": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "missing": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "missing_checks": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "model": {
+      "type": "string"
+    },
+    "object": {
+      "const": "chat.completion",
+      "type": "string"
+    },
+    "partial_evidence": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "receipt": {
+      "additionalProperties": true,
+      "properties": {
+        "how_to_verify": {
+          "type": "string"
+        },
+        "issued_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "issuer": {
+          "type": "string"
+        },
+        "issuer_key": {
+          "type": "string"
+        },
+        "key_id": {
+          "type": "string"
+        },
+        "result_hash": {
+          "type": "string"
+        },
+        "service": {
+          "type": "string"
+        },
+        "signature": {
+          "type": "string"
+        },
+        "signed_message": {
+          "type": "string"
+        },
+        "standard": {
+          "const": "eucompliance-receipt/2",
+          "type": "string"
+        },
+        "subject": {
+          "type": "string"
+        },
+        "valid_until": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "verify_url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "standard",
+        "service",
+        "subject",
+        "result_hash",
+        "issued_at",
+        "valid_until",
+        "issuer",
+        "issuer_key",
+        "key_id",
+        "verify_url",
+        "how_to_verify",
+        "signature",
+        "signed_message"
+      ],
+      "type": "object"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "settled": {
+      "description": "When present on an error, false means no settlement occurred.",
+      "type": "boolean"
+    },
+    "status_code": {
+      "type": "integer"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "unknown": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "usage": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "x402_service": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

AddedAug 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already signal read-only and open-world behavior, and the description adds valuable context: exact cost per call, OpenAI compatibility, free JSON validation, and no required account/API key. These are meaningful behavioral traits beyond the annotations, especially the billing implication and access model.

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

Conciseness5/5

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

The description is two concise sentences with no filler. Key information—capabilities, cost, compatibility, validation, and auth requirements—is front-loaded and each clause earns its place.

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?

The description covers the main purpose, cost, access, and validation workflow, and an output schema exists so return values need not be explained. However, it lacks parameter documentation and explicit guidance on when to choose micro over the sibling agentllm tools, leaving an agent with some ambiguity in a crowded tool family.

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 carries the burden of explaining prompt, system, and max_tokens. It offers no direct parameter info; only the phrase 'OpenAI-compatible' hints at standard chat-completion semantics. Parameter names are somewhat self-explanatory, but this does not compensate for the complete lack of explicit descriptions.

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 states a specific set of use cases (classification, extraction, routing, short summaries) with a clear resource and cost, making the tool's purpose evident. It does not explicitly name sibling tools like agentllm_basic or agentllm_plus, so differentiation relies on the 'micro' title and the fixed low price rather than an explicit comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context: small, cheap, OpenAI-compatible tasks and a free JSON validation step with no account or API key. However, it does not explicitly say when to prefer this tool over agentllm_basic/plus, nor does it state any exclusions or conditions when another tool should be used instead.

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

All Agent Decision & Evidence Tools (MCP + x402) 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.