Skip to main content
Glama
Sign In

Agentalog — Agent Auto Log

by com.agentalog
OverviewDiscussionsAdmin

Create listing

create_listing

Submit an MCP server, skill or plugin for review. Free with an account; US$ 0.10 without one. Limit: one submission a day and three in the queue per owner. Automatic review approves supported low-risk MCP listings; uncertain cases wait for a person. Poll status_api (GET /api/listings/:id/status, no credential) to learn the decision. A person or agent can submit without an account for US$ 0.10, paid through x402 or prepaid credit; with an account, it is free. Each owner can submit once a day and keep up to three submissions in the queue. For a skill, provide its SKILL.md URL. The service checks the body and quota before charging. An invalid body returns 400; an exhausted quota returns 429.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>",
      "url": "<url>"
    },
    "name": "create_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesMCP endpoint, SKILL.md URL, the plugin's repository or the OKF bundle's `index.md`. For an OKF bundle on a domain you control, `POST /api/okf/ping` is free.
bodyNoLong description, optional.
kindYesWhat is being registered.
nameNoDisplay name; without it, taken from the source.
taglineNoOne line saying what it is for.
categoryNoCategory so the listing shows up under the right filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / session_token
      Removed value: -{
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "mcp",
-  "skill",
-  "plugin"
-]New value: +[
+  "mcp",
+  "skill",
+  "plugin",
+  "okf"
+]
    • changedInput schema / properties / url / description
      Previous value: -"MCP endpoint, SKILL.md URL or the plugin's repository."New value: +"MCP endpoint, SKILL.md URL, the plugin's repository or the OKF bundle's `index.md`. For an OKF bundle on a domain you control, `POST /api/okf/ping` is free."
  3. Changed7 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"Long description, optional."
    • addedInput schema / properties / category / description
      Added value: +"Category so the listing shows up under the right filter."
    • addedInput schema / properties / kind / description
      Added value: +"What is being registered."
    • addedInput schema / properties / kind / enum
      Added value: +[
+  "mcp",
+  "skill",
+  "plugin"
+]
    • addedInput schema / properties / name / description
      Added value: +"Display name; without it, taken from the source."
    • addedInput schema / properties / tagline / description
      Added value: +"One line saying what it is for."
    • addedInput schema / properties / url / description
      Added value: +"MCP endpoint, SKILL.md URL or the plugin's repository."
  4. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations: reveals that review is automatic for low-risk MCP listings with human fallback, that the body and quota are validated before charging, that payment is via x402 or prepaid credit, and that invalid bodies return 400 while exhausted quotas return 429. This is exactly the operational context an agent needs before initiating a paid, non-idempotent mutation.

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

Conciseness3/5

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

Front-loads purpose and pricing well, but the second half repeats the same two facts almost verbatim: 'Free with an account; US$ 0.10 without one' is restated as 'with an account, it is free... without an account for US$ 0.10', and the one-per-day/three-in-queue limit is stated twice. Roughly a third of the text is redundant.

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

Completeness4/5

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

With no output schema, the description compensates by explaining how to learn the decision via status_api. Adequate for a mutation tool whose annotations already cover safety. It never says what the submission returns (e.g., a listing id) that status_api's :id would require, which is a minor but real gap.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all six parameters thoroughly, including the url semantics for each kind. The description only adds the skill-specific SKILL.md URL hint, which is largely a restatement. Baseline 3 applies.

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?

Opens with a specific verb and resource: 'Submit an MCP server, skill or plugin for review.' Clear against most siblings like get_listing or list_listings. However it omits 'okf' from the enumerated kinds even though the schema enum includes it, and the closest sibling submit_okf is never mentioned, leaving a small ambiguity about which tool owns OKF submissions.

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

Usage Guidelines4/5

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

Explains the account-vs-no-account path, the cost of each, the quota, and points to status_api with an explicit endpoint and 'no credential' note for checking the outcome. It also states the skill-specific requirement (SKILL.md URL). No explicit when-not-to-use or sibling routing (e.g., submit_okf for OKF bundles), so it falls short of a 5.

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

All Agentalog — Agent Auto Log toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources