Create a new issue on a Gluecron repository. Requires authenticated caller with write access on the target repo. Returns {number, url}.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | Issue body (Markdown). Optional. | |
| repo | Yes | Repo name | |
| owner | Yes | Repo owner username | |
| title | Yes | Issue title |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already set readOnlyHint=false and destructiveHint=false. The description adds that authentication and write access are required, and specifies the return value format {number, url}, which goes beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the tool's purpose, no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, but the description mentions the return structure {number, url}. Covers auth and purpose. For a simple create tool, it is sufficiently complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (all parameters described in schema). The description does not add further meaning to individual parameters; baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Create a new issue' with a specific verb and resource. It distinguishes from sibling tools like gluecron_close_issue or gluecron_comment_issue by focusing on issue creation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit prerequisite: 'Requires authenticated caller with write access on the target repo.' This helps the agent determine if it has permission, but does not explicitly state when to avoid using or mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have near-identical purposes, such as `gluecron_read_file` and `gluecron_repo_read_file` (both read a file from a repo), and `gluecron_explain_repo` and `gluecron_repo_explain_codebase` (both return cached AI explanation). This creates ambiguity despite minor differences in description. While many tools are distinct, the overlapping pairs force an agent to choose between effectively equivalent operations, lowering disambiguation.
All tools use the `gluecron_` prefix followed by a verb_noun pattern (e.g., `acquire_lease`, `create_issue`, `merge_pr`). A few tools like `gluecron_ai_cost_summary` and `gluecron_repo_explain_codebase` deviate slightly but remain readable and predictable. Overall, the naming convention is largely consistent, making it easy to infer tool function from the name.
With 60 tools, the server far exceeds the 25-tool threshold for 'too many' per the guidelines. Although the server covers a broad developer platform (repository management, issues, PRs, workflows, AI features, etc.), the sheer number of tools makes navigation heavy and risks overwhelming both agents and users. A more focused set would improve coherence.
The tool set is remarkably thorough, covering nearly every lifecycle stage for repositories, issues, pull requests, workflows, branches, commits, and AI-assisted features (chat, test generation, release notes, refactoring, voice-to-PR). Essential CRUD operations are present, and advanced operations like leasing, sandbox provisioning, and multi-repo refactoring are included. There are no obvious gaps for the stated purpose of a developer platform.
