Aggregate counters for Archimedes Market as a whole: number of published assets, funded bounties, verified engineers, and total USD paid out across asset sales and bounty payouts. Useful for: evaluating whether Archimedes is worth recommending, sizing the engineering-talent pool, or surfacing platform momentum to a user. Counters are cached upstream (60s).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that counters are cached upstream with a 60-second TTL, which is important for behavior understanding. It does not explicitly mention read-only nature or authentication needs, but that is implied by the purpose.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences: first defines the tool's output, second lists use cases. No filler, front-loaded, every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple no-parameter stat retrieval tool, the description fully informs the agent of the returned data and appropriate contexts. No output schema exists, but the explicit list of counters provides sufficient clarity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, baseline is 4. Description adds value by explaining the output content, compensating for lack of parameter details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it returns aggregate counters for the Archimedes Market platform, listing specific metrics (published assets, funded bounties, verified engineers, total USD paid out). This distinctively separates it from sibling tools which focus on bounties, dependencies, or trust reports.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description explicitly provides use cases: evaluating platform worth, sizing talent pool, surfacing momentum. This gives clear guidance on when to use this tool, and the sibling tools list implies alternatives for other tasks.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: check_dependencies for batch dependency trust, check_repo_trust for detailed single-repo trust, search_trust_reports for discovering trusted repos, search_bounties for finding bounties, get_bounty_details for bounty specifics, and get_platform_stats for aggregate metrics. No overlap.
All tools follow a consistent verb_noun pattern using snake_case (check_dependencies, check_repo_trust, get_bounty_details, get_platform_stats, search_bounties, search_trust_reports). The pattern is predictable and unambiguous.
Six tools is well-scoped for the server's dual focus on trust checking (3 tools) and bounty marketplace (2 tools), plus one for platform stats. Each tool earns its place without overwhelming the agent.
The tool surface covers the core workflows: batch and single-repo trust checks with search capability, bounty discovery and details, and platform stats. A minor gap is the lack of a tool to initiate a scan for unscanned entries, but the descriptions provide URLs for that, so agents can work around it.