Skip to main content
Glama

Stratalize Intelligence

Get Github Ecosystem Intelligence

get_github_ecosystem_intelligence
Read-only

Use when assessing a technology vendor open-source presence, evaluating developer community strength, or researching a company GitHub footprint before a technical due diligence. Returns organization profile and top repository stats — stars, forks, contributors, and language breakdown. Example: HashiCorp GitHub — 18 public repos, Terraform at 38,000 stars, 147,000 forks, 2,800 contributors — strong community signal supporting enterprise adoption thesis. Source: GitHub public API. $0.02 USDC per call.

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": {
      "org_or_company": "<org_or_company>"
    },
    "name": "get_github_ecosystem_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_or_companyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, and non-destructive behavior. The description adds useful context beyond annotations: the data source (GitHub public API), the returned metrics (stars, forks, contributors, language breakdown), and a per-call cost of $0.02 USDC. It does not discuss rate limits or pagination, but the added cost and source information is valuable.

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?

The description is front-loaded with usage guidance and then covers return values, an example, source, and cost. The example is helpful but somewhat lengthy; overall it is well-structured and mostly free of redundant wording.

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 read-only, single-parameter tool with no output schema, the description covers what is returned, the data source, and the pricing. The main gap is clearer input format guidance for the parameter, but otherwise an agent has enough information to invoke it correctly.

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?

With only one parameter and 0% schema description coverage, the description must compensate. The example ('HashiCorp GitHub') implies that the input should be an organization or company name, but the description does not explicitly state the accepted format or whether it resolves company names to GitHub organizations. It adds some meaning but leaves ambiguity.

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-resource pair ('get GitHub ecosystem intelligence') and explains what the tool returns: organization profile and top repository stats. It does not explicitly differentiate from sibling intelligence tools, but the GitHub-specific focus makes its purpose clear.

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

Usage Guidelines4/5

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

It provides clear when-to-use guidance: assessing vendor open-source presence, evaluating developer community strength, and researching GitHub footprint before technical due diligence. It does not state when not to use it or name alternative tools, but the context is sufficiently specific.

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