Skip to main content
Glama
Sign In

agentstock

by dev.agentstock
OverviewDiscussionsAdmin

Search stock media

search_assets
Read-onlyIdempotent

Semantic search over AI-generated images and videos. An empty query lists the newest assets. Returns captions, tags, dimensions, aspect ratio, price in USDC, a thumbnail URL, a watermarked preview clip for videos, the paid download_url, and license fields (license, release_safe, has_text, ai_generated, ai_disclosure).

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": "search_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
typeNo
queryNoNatural-language description, e.g. "neon cyberpunk alley at night".
per_pageNo
aspect_ratioNoExact label such as "16:9", "1:1", "9:16".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive profile, so the description's job is to add context — and it does: it discloses the watermarked preview versus the paid download_url, and the license fields that gate reuse. It stops short of stating pagination behavior or result-count limits, 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.

Conciseness4/5

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

Three sentences, front-loaded with purpose and followed by capability and payload. The return-field enumeration is long but earns its place because no output schema exists; it reads as a dense list rather than padding.

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?

With no output schema, enumerating the returned fields (captions, tags, dimensions, price in USDC, preview vs download, license flags) is exactly the missing context an agent needs. The remaining gap is pagination and total-result semantics for a paged search tool.

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 only 40%, so the description should compensate, but it explains no parameters beyond the empty-query behavior for 'query'. The enum for type, the aspect_ratio label format, and the meaning/bounds of page and per_page are left entirely to 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?

States a specific technique and resource ('Semantic search over AI-generated images and videos'), which is clearly distinct from the sibling get_asset (single-item fetch) and the set tools. An agent can route between these without opening a schema.

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?

The single cue 'An empty query lists the newest assets' implicitly tells the agent it can browse without a query, which is useful. However, there is no explicit guidance on when to prefer this over get_asset or list_sets, and no mention of how paging through results should be driven.

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

All agentstock 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