Skip to main content
Glama

Apex Score

apex_score
Read-onlyIdempotent

Scores Web3 projects across five dimensions—team, traction, tokenomics, market, security—and provides a breakdown with actionable recommendations to streamline due diligence.

Instructions

Run the Apex Copilot DD pre-screen on a Web3 project. Scores against five dimensions (team 20%, traction 25%, tokenomics 20%, market 20%, security 15%) and returns a breakdown plus actionable recommendations. A score of 85 or above shortens manual due diligence when the project later engages with Apex. The agent should extract short excerpts from the founder's deck or whitepaper locally and pass them as files[].excerpt. Full file contents must NOT be transmitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNameYesProject name (2-200 chars)
projectUrlNoPublic project URL (optional)
descriptionNoProject description, ideally including problem, solution, target user, current stage
filesNoFile summaries (up to 20). Names + sizes + short excerpts only — no full contents.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue if scoring completed successfully.
scoreOverallNoComposite 0-100 score across all dimensions.
breakdownNoSub-scores by dimension, each 0-100.
summaryNoShort narrative summary.
recommendationsNoActionable steps to improve the score or de-risk the project.
Behavior5/5

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

Annotations already indicate read-only and idempotent. The description adds that a score of 85+ shortens manual DD later, and reinforces the excerpt-only rule. No contradictions.

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

Conciseness5/5

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

Three concise sentences, front-loaded with purpose, and every sentence adds value. No fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description adequately explains the tool's behavior and output (breakdown + recommendations). Sufficient for an agent to invoke 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?

Schema description coverage is 100%, so baseline is 3. The description repeats what the schema already says about files[].excerpt but does not add new semantic meaning beyond the schema.

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 clearly states the tool runs a DD pre-screen on Web3 projects, scoring against five dimensions, and returns a breakdown plus recommendations. This is specific and distinguishes it from siblings like apex_code_review or apex_fund_match.

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

Usage Guidelines5/5

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

Provides explicit guidance: extract short excerpts locally and pass as files[].excerpt, with a warning not to transmit full file contents. This tells the agent exactly how to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Apex-Foundation/copilot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server