Skip to main content
Glama

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. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, destructiveHint=false), and the description adds genuinely new behavioral facts: the underlying data source ('GitHub public API') and a per-call cost of $0.02 USDC, which matters for budget-aware invocation. It does not say what happens when the org has no GitHub presence or whether data is cached/fresh, leaving error and recency behavior undisclosed.

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?

Front-loaded with usage triggers, then outputs, then a worked example, then source and price — a sensible ordering with no filler sentences. The HashiCorp example is somewhat verbose with illustrative numbers, but it is the only place input format is hinted at, so it earns most of its length.

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?

With one parameter, no output schema, and annotations already declaring a safe read, the description does enough: it names the returned fields and the data source. The remaining gaps are the input format ambiguity and failure/empty-result behavior, which are modest rather than disqualifying for a single-parameter lookup.

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 0% for the single parameter, so the description carries the full burden of explaining 'org_or_company'. The HashiCorp example implies a company name is acceptable and gives a feel for expected input, but it never clarifies slug format versus free-text company name, or how resolution works when no exact org matches — a real ambiguity given the name explicitly allows either.

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 resource and output ('Returns organization profile and top repository stats — stars, forks, contributors, and language breakdown') plus concrete use triggers, so the agent knows this is the GitHub/OSS-presence tool rather than a general company or financial intelligence tool. It stops short of explicitly contrasting with adjacent siblings like get_company_intelligence_synthesis or get_portfolio_vendor_intelligence, which share the due-diligence framing.

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?

Three explicit when-to-use conditions are given: vendor OSS presence assessment, developer community strength, and pre-due-diligence footprint research. There are no when-not conditions and no named alternates for the overlapping due-diligence siblings, so the agent must infer the boundary.

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