Skip to main content
Glama

submit_project

Suggest a product for the directory. The submission is saved as pending and reviewed against published criteria; nothing is published automatically.

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>",
      "one_liner": "<one_liner>",
      "why_try": "<why_try>",
      "category": "<category>"
    },
    "name": "submit_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesOfficial website or app-store URL.
nameYes
tagsNo
contactNoOptional private email.
why_tryYesWhat a user can do with the free option.
best_forNoOptional. Who it is for. If omitted it is taken from why_try and shortened at a word end.
categoryYes
logo_urlNoOptional public URL of a square logo (PNG, JPG, WebP or GIF, up to 2 MB). Resized to 256x256; fetch failures never reject the submission.
one_linerYes
agent_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / best_for
      Added value: +{
      +  "description": "Optional. Who it is for. If omitted it is taken from why_try and shortened at a word end.",
      +  "maxLength": 160,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "utilities",
      -  "productivity",
      -  "developer",
      -  "education",
      -  "sports",
      -  "environment",
      -  "ai-agents"
      -]New value: +[
      +  "ai-agents",
      +  "developer",
      +  "design-media",
      +  "productivity",
      +  "business",
      +  "finance",
      +  "games",
      +  "education",
      +  "health",
      +  "utilities"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / logo_url
      Added value: +{
      +  "description": "Optional public URL of a square logo (PNG, JPG, WebP or GIF, up to 2 MB). Resized to 256x256; fetch failures never reject the submission.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does a decent job: it discloses that this is a mutation whose result is a pending entry, that moderation against published criteria follows, and explicitly that nothing goes live automatically. It omits auth/permission requirements, duplicate or resubmission behavior, and the review turnaround, which keeps it out of 5 territory.

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?

Two tight sentences, front-loaded with the action and followed by the outcome. Every clause carries information and nothing is padding.

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?

It covers purpose and post-submission outcome, which are the essentials, but for a 10-parameter mutation with no annotations and no output schema it leaves too much open: what a valid submission contains, what happens on rejection, and what the caller receives back after submitting.

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?

Ten parameters with only 50% schema description coverage, and the description mentions none of them. Half the fields (name, tags, category, one_liner, agent_name) have no explanation anywhere, so the description should be compensating for the coverage gap but instead says nothing about what a good submission looks like or what the required fields demand.

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?

States a specific verb and resource ('Suggest a product for the directory') and the action is unambiguously the only write operation among read-only siblings like get_project, search_projects and list_categories. It stops short of naming any sibling explicitly, so the differentiation is inferred from the shared resource name rather than stated.

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 the create/submit use case but gives no explicit when-to-use or when-not-to guidance, and never points to the sibling tools that would sensibly precede a submission (search_projects to check for duplicates, run_launch_check for eligibility). A 'one product per entry, search first' note is the kind of guidance an agent needs and does not get.

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.