Skip to main content
Glama
ARKOSCOPE Public Sources MCP

ARKOSCOPE Public Sources MCP

Official
by arkoscope

get_project_sources

Read-onlyIdempotent

Retrieve public source URLs and evidence levels for an exact crypto project name, ticker, or ID; unknown inputs are rejected instead of guessed.

Instructions

Return an exact project name, ticker or id with public source URLs and evidence levels. Unknown inputs are not guessed. Does not fetch URLs or certify safety.

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": {
      "project": "<project>"
    },
    "name": "get_project_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral facts: no guessing on unmatched inputs, no URL fetching, no safety certification. This sets expectations about failure and scope limits that the annotations cannot express.

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, front-loaded with the outcome and followed by two scope limits. No filler, and each sentence carries distinct information.

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?

For a one-parameter lookup with strong annotations and no output schema, the description conveys the shape of the return (source URLs and evidence levels) and the key caveats. Only minor gaps remain around ambiguity handling and result volume.

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 coverage is 0% and the single parameter is only typed as a 1-80 character string, so the description's mention of 'name, ticker or id' is real added meaning about accepted identifier forms. It stops short of saying how matching works (case sensitivity, ambiguity handling), so baseline-plus rather than rich.

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 ('Return') and resource (exact project name, ticker or id) plus what accompanies it (public source URLs, evidence levels). The 'exact' resolution framing implicitly distinguishes it from a listing tool like list_projects, though the sibling is never named.

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?

Gives useful boundaries — unknown inputs are not guessed, URLs are not fetched, safety is not certified — which tells an agent when this tool will fail or fall short. However, it never states when to prefer it over list_projects or what to do instead when a lookup is ambiguous.

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