Skip to main content
Glama
Sign In
arena-mcp

arena-mcp

by vortep-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Are.na

arena_search

Search Are.na for visual references across channels, image blocks, and users, returning image URLs and direct Are.na links for design inspiration.

Instructions

Search Are.na (visual references: channels, image blocks, users). Returns compact objects with an image URL and an are.na link. Works without a token.

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": {
      "query": "<query>"
    },
    "name": "arena_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
perNo
pageNo
typeNoWhat to search: all — everything, channels — collections, blocks — individual images/links, users — authorsall
queryYesSearch query, e.g. "mobile onboarding" or "dashboard ui"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations present, the description carries the behavioral transparency burden. It usefully discloses that no token is needed and that results are compact objects containing an image URL and an Are.na link, but it omits other behavioral details such as pagination behavior, response limits, or type-specific result differences.

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?

The description is three short sentences, front-loaded with the tool's purpose, followed by output shape and auth requirement. Every sentence earns its place and there is no fluff or repetition.

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 simple search tool the description covers the main idea, but with no output schema and no annotations it stops short of full completeness. It omits pagination semantics, exact fields of the returned objects, and any error or empty-result behavior, which an agent would need for robust usage.

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?

The schema describes 'query' and 'type' with helpful detail, but schema coverage is only 50%. The description adds no information about the pagination parameters 'per' and 'page', which remain undocumented in both the schema and the description, so the agent gets no semantic guidance for those parameters.

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?

The description names a specific action ('Search') and a clear resource ('Are.na'), and scopes it to visual references: channels, image blocks, and users. It distinguishes itself from the sibling tools by presenting a broad search over those three categories, though it does not explicitly name any sibling or contrast itself with direct-fetch tools.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives such as arena_block, arena_channel, or arena_channel_contents. The phrase 'Search Are.na' implies a query-driven use case, and 'Works without a token' gives some context, but there are no when-to-use or when-not-to-use instructions.

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