Skip to main content
Glama
ARKOSCOPE Public Sources MCP

ARKOSCOPE Public Sources MCP

Official
by arkoscope

list_projects

Read-onlyIdempotent

Retrieve projects from the bundled, dated ARKOSCOPE public registry, with optional text and wave filters to narrow results. Use it for read-only access to public project source data.

Instructions

List projects in the bundled, dated public ARKOSCOPE registry. Optional bounded text filter. No live feed or private API access.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
waveNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/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 closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the data is a bundled, dated snapshot rather than a live feed, and the filter is bounded. It omits pagination or result-size behavior, 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.

Conciseness5/5

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

Three short sentences, zero filler, with the registry scope front-loaded before the filter and the negative constraint. Every clause carries distinct information.

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

Completeness3/5

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

For a two-optional-parameter list tool with no output schema and full annotation coverage, the description covers scope and data freshness adequately. The unexplained 'wave' parameter is the significant remaining hole an agent would need to resolve before calling.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain both parameters. It addresses only the text filter ('Optional bounded text filter'), matching the query parameter's 80-char bound, and never mentions 'wave' or its 1-3 range, leaving half the parameters undocumented.

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 verb and resource ('List projects') plus the exact data scope ('bundled, dated public ARKOSCOPE registry'), which distinguishes it from the sibling get_project_sources. It stops short of explicitly contrasting with that sibling, so it lands at 4 rather than 5.

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?

'No live feed or private API access' sets a clear negative boundary, telling the agent this only serves the static public snapshot. However, there is no positive when-to-use guidance and no named alternative for cases needing live or private data, so usage is only implied.

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

Deploy Server

Other Tools