Skip to main content
Glama

Submit a tool

submit_tool
Idempotent

Suggest a GitHub repository (an AI agent, MCP server or AI developer tool) for listing on AgentIndex. No login or API key needed. The submission is queued for human review, usually within 1-3 days; it does not appear in search results immediately. Tools are listed only if the repository is public and has at least 100 stars. Check with search_tools first that the tool is not already listed. Returns {success, message, github_url}, or an isError result if the URL is not a GitHub repository URL or the submission service is unavailable.

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

Input Schema

NameRequiredDescriptionDefault
emailNoOptional address that receives an email when the review is done. Only send it if the user provided it.
github_urlYesRepository URL in the form https://github.com/<owner>/<repo>, e.g. https://github.com/modelcontextprotocol/servers.

Output Schema

NameRequiredDescriptionDefault
messageYes
successYes
github_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"Contact email for review updates (optional)"New value: +"Optional address that receives an email when the review is done. Only send it if the user provided it."
    • addedInput schema / properties / email / format
      Added value: +"email"
    • changedInput schema / properties / github_url / description
      Previous value: -"GitHub repository URL (e.g. https://github.com/owner/repo)"New value: +"Repository URL in the form https://github.com/<owner>/<repo>, e.g. https://github.com/modelcontextprotocol/servers."
    • addedInput schema / properties / github_url / pattern
      Added value: +"^https://github\\.com/[^/\\s]+/[^/\\s]+/?$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "github_url": {
      +      "type": "string"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, idempotentHint=true, openWorldHint=true). The description adds genuinely new behavior: the submission is queued for human review in 1-3 days, does not appear in search immediately, and returns an isError result when the URL is not a GitHub repo URL or the service is down. That is real operational context beyond the annotations.

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

Conciseness4/5

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

Front-loaded with the core action in the first clause, then prerequisites, timing, and return shape. Information-dense with little waste, though it is a very long single paragraph and the return-shape sentence is somewhat redundant given an output schema exists.

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?

Covers identity, eligibility, timing expectations, duplicate-check guidance, and error conditions for a two-parameter tool with an output schema. An agent has everything needed to decide whether and how to invoke it; nothing material is missing.

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

Parameters4/5

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

Schema coverage is 100% (both parameters fully documented, including the email 'only send if the user provided it' caveat), so the baseline is 3. The description adds semantic value by explaining what makes a github_url acceptable at the tool level (public GitHub repo, 100+ stars) and what failure looks like, going beyond the regex pattern in 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 and resource ('Suggest a GitHub repository ... for listing on AgentIndex') and scopes the acceptable inputs (AI agent, MCP server, AI developer tool). An agent can distinguish this submission tool from the read-only siblings like search_tools and get_tool_detail without inspecting any 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?

Explicitly says to check search_tools first to avoid duplicate submissions, states no login/API key is needed, and gives the eligibility gate (public repo with 100+ stars). This is exactly the when-to-use, prerequisite, and alternative guidance the dimension asks for.

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