Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

github_org

Retrieve a GitHub organization's public profile by login, including name, description, blog, location, repository count, followers, and verification status.

Instructions

Retrieve a GitHub organization profile. Returns the public profile of a GitHub organization by its required org login, with fields such as name, description, blog URL, location, public repository count, followers and whether the organization is verified.

Input Schema

NameRequiredDescriptionDefault
orgYesGitHub organization login

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It implies a safe read by calling the result the 'public profile' and enumerates the fields returned, which gives real behavioral signal. It still omits auth/rate-limit context, but for a simple public read tool this is adequate.

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?

Two sentences, front-loaded with the verb and resource; the field enumeration is long but information-dense and useful given there is no output schema. No filler.

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

Completeness4/5

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

For a single-parameter read tool with no output schema, the description compensates by listing the returned fields, which is exactly what the missing output schema would otherwise require. Only the lack of alternative-routing guidance keeps it from being complete.

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%, so the `org` parameter and its description are already fully documented. The description only restates that `org` is the required login, adding no format or syntax detail beyond the schema, which is the expected baseline.

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?

States a specific verb ('Retrieve') and resource ('GitHub organization profile') and even enumerates the returned fields, so the intent is unambiguous. It does not explicitly distinguish itself from close siblings such as github_user or github_org_repos, but 'organization profile' is a distinct enough resource that an agent can differentiate.

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 when-to-use guidance, no mention of when to prefer this over github_user (for individuals) or github_org_repos (for an org's repositories). The agent must infer the selection criteria from the 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