Skip to main content
Glama

Protocol forks

forks
Read-only

A protocol's forks: the protocols it forked its code from, and the live protocols that fork it ranked by TVL (USD), with the forks' count and combined TVL, 50 per page. Free data from AlphaGrowth (alphagrowth.io).

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": {
      "slug": "<slug>"
    },
    "name": "forks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 50 forks per page.
slugYesThe project's slug; find it with find_projects.

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 read-only, non-destructive, non-open-world profile, so the description only needs to add shape, which it does: pagination at 50 per page, TVL-based ranking, inclusion of fork count and combined TVL, and a free AlphaGrowth data source. Missing only whether every protocol is covered or what happens for protocols without forks.

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?

A single front-loaded sentence stating the resource first, then the returned fields and pagination; every clause carries information. It is dense and slightly run-on, but there is 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?

With no output schema, the description carries the burden of describing returns and does so: both fork directions, ranking metric, count, combined TVL, and page size. Only edge-case behavior (no forks, invalid slug) is left unstated for this simple two-parameter read tool.

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% and both parameters are documented there, including the '50 forks per page' note the description merely repeats. The description adds no extra meaning about slug format or valid page bounds beyond the schema, so baseline 3 applies.

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 the specific resource (a protocol's forks) and spells out both directions of the relationship: the code it forked from and the live protocols forking it, ranked by TVL. An agent knows exactly what data this returns without opening the 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?

Usage is only implied by the nouns: fetch a protocol's fork lineage. There is no explicit when-to-use, when-not, or alternative named (e.g., find_projects for resolving slugs is only mentioned in the schema). Adequate but leaves routing to inference.

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