Skip to main content
Glama

apex-dev

Github repo intel

github_repo_intel
Read-onlyIdempotent

GitHub repository info and maintenance health intelligence: stars, forks, open issues, primary language, license, latest release, days since last push, 0-100 health score, and ACTIVE/MAINTAINED/STALE/ARCHIVED verdict. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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": {
      "repo": "<repo>"
    },
    "name": "github_repo_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesGitHub owner/name or URL (e.g. x402-foundation/x402).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: a per-call price point and the x402 payment requirements including specific chains. It still doesn't disclose behavior on unauthenticated rate limits, missing repos, or archived-repo edge cases, which keeps it from a 5.

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?

It is front-loaded: the value proposition and return fields come first, payment mechanics last. The field enumeration is dense but each item tells the agent what to expect back. The payment-rail sentence is somewhat cluttered with chain names but is necessary for a priced tool.

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 no output schema, the description carries the return-value burden, and it does so by listing the metrics and the verdict scale. It also covers the payment prerequisite. What is missing is failure-mode context, e.g. behavior for private, deleted, or nonexistent repos, which matters for an open-world fetch tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by explaining the otherwise cryptic `payment` parameter's role in the two-step handshake and by naming the accepted payment rails and price. It adds little about the `repo` format, but the schema already covers that with examples.

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?

The description names a specific verb and resource ('GitHub repository info and maintenance health intelligence') and then enumerates exactly what it returns: stars, forks, open issues, language, license, latest release, days since last push, a 0-100 health score, and an ACTIVE/MAINTAINED/STALE/ARCHIVED verdict. That verdict vocabulary distinguishes it from sibling tools like package_audit or tech_stack_detect, which serve different analysis purposes.

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 gives a clear operational protocol: 'Call once without `payment` for terms, then call again with `payment`.' That tells the agent exactly the sequence, which is non-obvious for a paid tool. It does not say when to prefer this over adjacent siblings, nor does it state what to do on payment failure, so it stops short of full when/when-not guidance.

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