Skip to main content
Glama
Sign In

CrateWire

by com.cratewire
OverviewDiscussionsAdmin

Scan a link

scan_link

Start a CrateWire scan of a public Instagram post or reel, a TikTok video, or a DJ set link (YouTube, SoundCloud, Mixcloud). If CrateWire already has the result it is returned at no cost. Otherwise the scan uses this account's monthly scan allowance, exactly like pasting the link in the CrateWire app, and the result is ready later through find_known_tracks or get_set_tracklist. Check find_known_tracks first when the user only wants to know what is already identified.

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": {
      "url": "<url>"
    },
    "name": "scan_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
accept_partialNoScan only the part of a set your remaining monthly minutes cover.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate this is not read-only, is non-idempotent, and open-world. The description goes beyond by disclosing billing behavior (monthly scan allowance, free if cached), async result availability (ready later via find_known_tracks or get_set_tracklist), and that it behaves like pasting the link in the app.

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 tight sentences, front-loading the action, then cost/reuse, then routing to alternatives. Every sentence earns its place and follows a logical flow.

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 no output schema, the description covers the essential context: what URLs are valid, cost implications, asynchronous result retrieval, and when to prefer another tool. Annotations cover safety, so nothing critical is missing for correct invocation.

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?

Schema coverage is 50% with only accept_partial described. The description adds meaningful semantics for url by enumerating the link types the tool accepts, compensating for the missing schema description. It does not add further constraints beyond the schema's length limits.

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 (Start a scan) and the accepted resources (public Instagram post/reel, TikTok video, DJ set link from YouTube, SoundCloud, Mixcloud). Distinguishes from find_known_tracks, but does not differentiate from the sibling scan_links (plural), so sibling differentiation is incomplete.

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?

Explicitly tells the agent when to use an alternative: 'Check find_known_tracks first when the user only wants to know what is already identified.' Also explains cost/reuse behavior and where to retrieve results later, leaving little to inference.

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

All CrateWire toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources