Skip to main content
Glama

Codenation

Submit a tool for review

submit_tool

Submit a project to the Codenation review queue as a free listing. Nothing is published by this call: a person reviews every submission and may decline it. A free listing links to the project with rel="nofollow". Requires the project's name, its full https:// URL and a contact email for the reviewer; tagline, description and category are optional. Only call this when the user explicitly asks to submit a project they are responsible for. Returns the submission id, or an error result if a field is invalid or the site is already listed. Limited to 5 submissions per hour per client.

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": {
      "name": "<name>",
      "url": "<url>",
      "email": "<email>"
    },
    "name": "submit_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull project URL, starting with https://.
nameYesProject name.
emailYesContact email for the reviewer. Not published.
taglineNoOne line about what it does. Optional.
categoryNoCategory slug. Optional, defaults to dev-tools.
descriptionNoA few sentences about the project. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses the human review gate and possible decline, that nothing is published, the rel="nofollow" nature of the listing, the rate limit of 5 submissions per hour per client, and the return/error contract. These are exactly the operational traits an agent cannot derive from readOnlyHint=false and destructiveHint=false.

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?

Roughly five sentences, front-loaded with the action and its non-effect, then requirements, then the usage restriction, then return and rate-limit facts. No sentence is filler and no information is repeated verbatim from the schema.

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

Completeness5/5

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

For a six-parameter mutation with no output schema, the description covers everything an agent needs: effect (review queue, not published), preconditions, required fields, error outcomes, and the returned submission id. Nothing material is left to inference.

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 all six parameters are already documented, including the https:// requirement and the 'Not published' note on email. The description only restates the required/optional split without adding format, default (category defaults to dev-tools), or validation detail beyond the schema, so the baseline of 3 applies.

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?

The first sentence gives a specific verb and resource ('submit a project to the Codenation review queue as a free listing') and immediately scopes the effect ('nothing is published'). It is clearly the only write operation among read-only siblings such as get_tool and search_tools, so an agent can distinguish it without opening the schema.

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

Usage Guidelines5/5

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

It states an explicit precondition: 'Only call this when the user explicitly asks to submit a project they are responsible for,' which both authorizes the call and excludes proactive/agent-initiated submissions. It also implies the failure mode when the site is already listed, giving the agent a reason to check first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources