Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Get organization

gitea_get_organization
Read-only

Fetch a Gitea organization's details by name from a specified site to inspect its profile and settings.

Instructions

[UNIFIED] Get information about a Gitea organization by name.

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": {
      "site": "<site>",
      "org": "<org>"
    },
    "name": "gitea_get_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYes
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.7/5.0
Behavior2/5

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

The readOnlyHint=true annotation already covers the safety profile, so the description's only job is to add context — and it adds none. It says nothing about what organization data is returned, whether private orgs are visible, or how a missing org surfaces. The '[UNIFIED]' prefix is unexplained and conveys no behavior.

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 short sentence that is front-loaded with the action and resource — nothing is buried. The unexplained '[UNIFIED]' tag is wasted tokens, but the sentence otherwise has no padding.

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

Completeness2/5

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

With no output schema, the description carries the burden of describing the returned organization shape, and it does not. Combined with an undocumented 'site' parameter and no error semantics, an agent can guess the call but not what it will get back.

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?

Schema description coverage is 0% for two required parameters. 'By name' loosely implies that 'org' is a name/slug rather than a numeric ID, but the 'site' parameter is completely undefined in both schema and description, leaving the agent to guess its format and purpose.

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 states a specific verb and resource (get information about an organization) and adds the lookup key (by name), so an agent knows this is a read-by-identifier tool. It does not distinguish itself from siblings like gitea_get_repository or gitea_get_user, but the resource noun is specific enough to be unambiguous.

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?

There is no guidance on when to use this versus related lookups, no prerequisites (e.g., does the caller need org membership or admin rights?), and no mention of failure behavior when the organization does not exist. The agent must infer all usage context.

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