Crawlora MCP

github_repo_languages

Read-only

Returns the language byte breakdown for a repository, sorted by bytes descending (tech fingerprint). owner: Repository owner (user or org login). repo: Repository name. Use github_repo_contributors to list a repository's contributors.

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": "github_repo_languages"
  }
}

Input Schema

Name	Required	Description	Default
`repo`	Yes	Repository name.
`owner`	Yes	Repository owner (user or org login).

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.6/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 the sorting behavior (bytes descending), which is useful, but discloses nothing about auth, rate limits, or behavior when a repo is empty/private. It neither contradicts nor substantially enriches the annotations.

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

Conciseness3/5

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

Front-loaded with the purpose, which is good, but the inline parameter descriptions duplicate the schema exactly and the contributors pointer is of questionable relevance. Short overall, but a sentence's worth of content is wasted.

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?

An output schema exists, so return values needn't be described, and the purpose plus parameter roles are fully covered. The only minor gap is that the sibling reference is not a genuine alternative, leaving an agent without guidance on how this tool composes with the other github_repo_* readers.

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 description coverage is 100%, both parameters are documented in the schema, and the description merely repeats those descriptions verbatim ("owner: Repository owner (user or org login). repo: Repository name."). No format, casing, or edge-case semantics are added 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.

Purpose5/5

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

States a specific verb and resource ("Returns the language byte breakdown for a repository") and adds the sort order, plus labels it a "tech fingerprint." An agent can distinguish this from github_repo, github_repo_forks, and github_repo_releases without inspecting any schema.

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

Usage Guidelines3/5

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

The description names a sibling (github_repo_contributors) but that reference is tangential — it routes to a different data domain (contributors), not a true alternative for language data. There is no explicit when-to-use or when-not-to-use guidance, so usage is only implied by the purpose statement.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?