PyScrappy

Overview Schema Source Related Servers Discussions Admin

Get Crypto

get_crypto

Fetch live cryptocurrency prices, market cap, and 24h change for specific coins or top market cap listings, with customizable currency and result limits.

Instructions

Fetch live cryptocurrency market data and return a list of coin records, each with fields: id, symbol, name, current price (in vs_currency), market cap, and 24h price change (percent).

Fetches from a live crypto market data API over the network, so results reflect current prices and require internet access; no local state is read or written. When query is omitted, returns the top coins ranked by market cap. If no coins match the query, returns an empty list rather than raising.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	String of comma-separated coin ids. Example: "bitcoin, ethereum". Default None (returns top coins by market cap).
`max_results`	No	Integer maximum number of coins to return. Example: 10. Default 20.
`vs_currency`	No	String fiat or quote currency code for prices, lowercase. Example: "usd". Allowed: any currency supported by the data source, e.g. "usd", "eur", "gbp", "jpy". Default "usd".	usd

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`count`	No
`errors`	No
`scraper`	No
`source_urls`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJul 31, 2026

changedInput schema / properties / max_results / description

Previous value: -"Max coins to return (default 20)."New value: +"Integer maximum number of coins to return. Example: 10. Default 20."

changedInput schema / properties / query / description

Previous value: -"Comma-separated coins (e.g. \"bitcoin, ethereum\"). Omit for top coins."New value: +"String of comma-separated coin ids. Example: \"bitcoin, ethereum\". Default None (returns top coins by market cap)."

changedInput schema / properties / vs_currency / description

Previous value: -"Fiat currency for prices, e.g. \"usd\", \"eur\" (default \"usd\")."New value: +"String fiat or quote currency code for prices, lowercase. Example: \"usd\". Allowed: any currency supported by the data source, e.g. \"usd\", \"eur\", \"gbp\", \"jpy\". Default \"usd\"."

Changed20 schema fields changedv1.3.3Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / max_results / description
```
Added value: +"Max coins to return (default 20)."
```
removedInput schema / properties / max_results / title
```
Removed value: -"Max Results"
```

addedInput schema / properties / query / description

Added value: +"Comma-separated coins (e.g. \"bitcoin, ethereum\"). Omit for top coins."

removedInput schema / properties / query / title
```
Removed value: -"Query"
```

addedInput schema / properties / vs_currency / description

Added value: +"Fiat currency for prices, e.g. \"usd\", \"eur\" (default \"usd\")."

removedInput schema / properties / vs_currency / title
```
Removed value: -"Vs Currency"
```
removedInput schema / title
```
Removed value: -"get_cryptoArguments"
```

removedOutput schema / $defs

Removed value: -{
-  "ToolError": {
-    "description": "A non-fatal problem encountered while scraping.",
-    "properties": {
-      "message": {
-        "title": "Message",
-        "type": "string"
-      },
-      "url": {
-        "title": "Url",
-        "type": "string"
-      }
-    },
-    "required": [
-      "url",
-      "message"
-    ],
-    "title": "ToolError",
-    "type": "object"
-  }
-}

removedOutput schema / properties / count / title
```
Removed value: -"Count"
```
removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
removedOutput schema / properties / errors / items / $ref
```
Removed value: -"#/$defs/ToolError"
```

addedOutput schema / properties / errors / items / description

Added value: +"A non-fatal problem encountered while scraping."

addedOutput schema / properties / errors / items / properties

Added value: +{
+  "message": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / errors / items / required
```
Added value: +[
+  "url",
+  "message"
+]
```
addedOutput schema / properties / errors / items / type
```
Added value: +"object"
```
removedOutput schema / properties / errors / title
```
Removed value: -"Errors"
```
removedOutput schema / properties / scraper / title
```
Removed value: -"Scraper"
```
removedOutput schema / properties / source_urls / title
```
Removed value: -"Source Urls"
```
removedOutput schema / title
```
Removed value: -"ScrapeToolResult"
```

Addedv1.2.0Jul 26, 2026
Removedv1.1.7Jul 26, 2026
AddedJul 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses that the tool makes a network call, requires internet, reads no local state, returns top coins when query is omitted, and returns an empty list rather than throwing on no matches. This meaningfully sets expectations, though it could also mention failure behavior on network errors.

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?

Two focused paragraphs with no filler. The return shape is front-loaded, the network/read-only behavior is stated next, and edge-case behavior is briefly covered. Every sentence earns its place.

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?

For a simple read-only lookup tool with three well-documented optional parameters and an output schema, the description is complete. It covers result shape, defaults, edge cases, and operational context without needing to restate schema details.

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

Parameters4/5

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

Input schema coverage is 100%, so the baseline is 3. The description adds value by clarifying that query is a comma-separated id list, that omission means top coins by market cap, and that prices are expressed in vs_currency. It complements rather than restates 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 uses a specific verb ('fetch') with a clear resource ('live cryptocurrency market data') and precisely enumerates the returned coin fields. It is immediately distinct from sibling tools like convert_currency or search_news, even without naming them.

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

Usage Guidelines4/5

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

The description establishes clear context: use this when you need current cryptocurrency prices, top coins by market cap, or coin lookups by id. It does not explicitly name alternatives or state when not to use it, but the intended domain is unmistakable from the first sentence.

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