Skip to main content
Glama
MCP Dokploy Online
by igoruam

github-one

Read-onlyIdempotent

Retrieves details for a specific GitHub integration by ID, helping you inspect or configure repository access for Dokploy deployments.

Instructions

GET /github.one

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": {
      "githubId": "<githubId>"
    },
    "name": "github-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
githubIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, and 'GET' is consistent with that, so there is no contradiction. However, the description adds nothing beyond those annotations: no indication of what the open-world fetch reaches, what happens when the ID is unknown, or what is returned.

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

Conciseness2/5

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

Extremely short, but brevity here reflects under-specification rather than density; there is no front-loaded statement of purpose. A bare route string is not a useful structure for an agent selecting a tool.

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

Completeness1/5

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

For a tool with a required identifier parameter, no output schema, and no clarifying annotations about return shape, the description supplies none of the information needed to call it confidently or distinguish results. It is effectively a stub.

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?

The single parameter githubId has 0% schema description coverage, so the description carries the full burden and adds nothing about what the ID identifies (numeric? slug? provider UUID?). The '.one' suffix in the route hints that the ID selects a single record, which is the only marginal semantic value contributed.

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

Purpose2/5

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

The description is just an HTTP route string, 'GET /github.one', which restates the tool name rather than explaining what resource is retrieved. The 'GET ... .one' pattern weakly implies a single-record lookup, so it is not fully meaningless, but an agent cannot tell what a 'github.one' record actually is or how it differs from github-getGithubRepositories or github-githubProviders.

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

Usage Guidelines1/5

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

There is no when-to-use guidance whatsoever — no conditions, no prerequisites, and no mention of any alternative among the many github-* siblings. The agent is left to infer everything from the route string and the parameter name alone.

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

Deploy Server

Other Tools