Skip to main content
Glama

Upstream.codes

Get repository

get_repository
Read-only

Repository details: visibility, default branch, description, fork and GitHub Sync state, and your permissions.

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": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "get_repository"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository slug.
ownerYesNamespace that owns the repository (user or organization handle).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by disclosing the field set returned, including the caller's own permissions and fork/GitHub Sync state, but says nothing about behavior on a missing/inaccessible repo or about rate limits.

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?

A single, compact sentence with the most useful content (the field list) up front and no filler. It is a noun fragment rather than a full sentence, which slightly weakens clarity about the action performed.

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?

For a simple two-required-parameter read tool with no output schema, the returned-field list is the key thing an agent needs, and it is present. However, nothing is said about failure modes (unknown repo, no access) or what 'your permissions' expands to, leaving gaps for an open-world tool.

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 coverage is 100% and both parameters (owner, repo) carry their own descriptions, so the baseline of 3 applies. The description adds no meaning beyond the schema, such as accepted owner formats or whether slugs are case-sensitive.

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?

The description names the resource and enumerates the specific data returned — visibility, default branch, description, fork/GitHub Sync state, and permissions — which tells an agent exactly what it gets back. It never uses a verb like 'retrieve' and does not differentiate itself from siblings such as list_repositories or get_file_contents, keeping it short of a 5.

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

Usage Guidelines2/5

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

No guidance on when to use this tool rather than alternatives like list_repositories or get_file_contents, and no preconditions (e.g., that owner/repo must exist) are stated. The agent must infer from the name alone that this fetches a single repository.

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