Altimateguide Agent MCP Server

submit_tool

Idempotent

Send a software tool to the Altimateguide directory for editorial review; submissions are queued as pending and are never published automatically.

Instructions

Submit a tool to the Altimateguide directory for editorial review (POST /api/agent/submit). The listing is queued as pending and is never published automatically — an editor reviews it. Categories are optional; unknown/empty categories are recorded for the reviewer. Requires a token (run complete_login, or set ALTIMATEGUIDE_AGENT_TOKEN).

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Canonical http(s) URL of the tool
`cons`	No	Short editorial cons
`name`	Yes	Tool name
`pros`	No	Short editorial pros
`proof`	No	Inclusion path (default none). sayabout (Wall of Love URL, recommended) and badge need verificationUrl. For a paid (dofollow) listing use upgrade_listing.
`source`	No	Origin id, e.g. agent:mcp
`pricing`	No	Starting price (USD)
`features`	No	Structured feature list (label + optional detail)
`freePlan`	No	Offers a free plan
`resubmit`	No	Set true to send a fresh copy after a previous submission for this URL was rejected. Mints a new idempotency key so the reviewer gets a new row instead of a replay of the rejected one.
`freeTrial`	No	Offers a free trial
`categories`	No	Category slugs — call list_categories to get valid ones
`externalId`	No	Your stable id for idempotent replays; derived from the URL when omitted
`description`	No	Neutral listing copy (min 20 chars; ranking language is rejected)
`verificationUrl`	No	Required for sayabout/badge proof
`categorySuggestions`	No	Free-text category hints when none of the real slugs fit; recorded for the reviewer

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedv1.0.3Oct 5, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / categories / description

Previous value: -"One or more category slugs"New value: +"Category slugs — call list_categories to get valid ones"

addedInput schema / properties / categories / items / minLength
```
Added value: +1
```

addedInput schema / properties / categorySuggestions

Added value: +{
+  "description": "Free-text category hints when none of the real slugs fit; recorded for the reviewer",
+  "items": {
+    "maxLength": 60,
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / cons

Added value: +{
+  "description": "Short editorial cons",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / description / description

Previous value: -"Neutral listing copy (min 20 chars; promotional/ranking language is rejected)"New value: +"Neutral listing copy (min 20 chars; ranking language is rejected)"

addedInput schema / properties / description / minLength
```
Added value: +20
```

changedInput schema / properties / externalId / description

Previous value: -"Your own id for idempotent replays"New value: +"Your stable id for idempotent replays; derived from the URL when omitted"

addedInput schema / properties / externalId / maxLength
```
Added value: +200
```
addedInput schema / properties / features / items / additionalProperties
```
Added value: +false
```
addedInput schema / properties / features / items / properties / description / maxLength
```
Added value: +300
```
addedInput schema / properties / features / items / properties / label / maxLength
```
Added value: +80
```
addedInput schema / properties / features / items / properties / label / minLength
```
Added value: +1
```

addedInput schema / properties / freePlan

Added value: +{
+  "description": "Offers a free plan",
+  "type": "boolean"
+}

addedInput schema / properties / freeTrial

Added value: +{
+  "description": "Offers a free trial",
+  "type": "boolean"
+}

addedInput schema / properties / name / minLength
```
Added value: +1
```

removedInput schema / properties / paymentRef

Removed value: -{
-  "description": "Required for paid proof",
-  "type": "string"
-}

addedInput schema / properties / pricing

Added value: +{
+  "additionalProperties": false,
+  "description": "Starting price (USD)",
+  "properties": {
+    "amount": {
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "currency": {
+      "const": "USD",
+      "type": "string"
+    },
+    "period": {
+      "enum": [
+        "month",
+        "year",
+        "one-time"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "amount",
+    "currency",
+    "period"
+  ],
+  "type": "object"
+}

changedInput schema / properties / proof / description

Previous value: -"Inclusion path (default none). sayabout/badge need verificationUrl; paid needs paymentRef."New value: +"Inclusion path (default none). sayabout (Wall of Love URL, recommended) and badge need verificationUrl. For a paid (dofollow) listing use upgrade_listing."

changedInput schema / properties / proof / enum

Previous value: -[
-  "none",
-  "sayabout",
-  "badge",
-  "paid"
-]New value: +[
+  "none",
+  "sayabout",
+  "badge"
+]

addedInput schema / properties / pros

Added value: +{
+  "description": "Short editorial pros",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / resubmit

Added value: +{
+  "description": "Set true to send a fresh copy after a previous submission for this URL was rejected. Mints a new idempotency key so the reviewer gets a new row instead of a replay of the rejected one.",
+  "type": "boolean"
+}

addedInput schema / properties / source / pattern
```
Added value: +"^[a-z0-9][a-z0-9:_-]{1,63}$"
```
addedInput schema / properties / url / format
```
Added value: +"uri"
```
addedInput schema / properties / verificationUrl / format
```
Added value: +"uri"
```

changedInput schema / required

Previous value: -[
-  "name",
-  "url",
-  "categories"
-]New value: +[
+  "name",
+  "url"
+]

First observedv1.0.1Oct 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true. The description adds genuinely new behavior beyond those: the listing is queued as pending, an editor must review it, it is never published automatically, and unknown categories are merely recorded for the reviewer. It still omits what the submission returns (e.g. an id or status) for a mutating call.

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?

Three tight sentences, front-loaded with purpose and endpoint, then review behavior, then category/auth prerequisites. No filler and nothing repeated from the schema.

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?

Covers the key non-obvious facts for a 16-parameter mutating tool with no output schema: pending review, auth prerequisite, optional categories. It does not describe the shape of the response or mention duplicate-checking, which an agent would need to call this well.

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 16 parameters including the resubmit idempotency nuance and the proof/verificationUrl pairing. The description only restates that categories are optional and unknown ones are recorded, adding little beyond the schema.

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

Purpose5/5

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

States a specific verb (submit) and resource (a tool listing to the Altimateguide directory) plus the concrete endpoint POST /api/agent/submit. The 'for editorial review' qualifier distinguishes it from upgrade_listing, the paid sibling.

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?

Gives clear context: submissions are queued as pending and never auto-published, categories are optional, and a token is required via complete_login or ALTIMATEGUIDE_AGENT_TOKEN. It does not, however, route the agent away from this tool when a duplicate exists (check_duplicate) or explicitly name upgrade_listing as the paid alternative in the description text itself.

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

Deploy Server

submit_tool

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools