Skip to main content
Glama
Sign In

42matters

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Fortytwo App Search

fortytwo_app_search
Read-onlyIdempotent

Search the app store by keyword and return matching apps with pagination. Example: fortytwo_app_search({ platform: "ios", query: "racing games", limit: 20, page: 1, _apiKey: "your-token" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page": 1,
      "limit": 20,
      "query": "racing games",
      "_apiKey": "your-42matters-api-key",
      "platform": "ios"
    },
    "name": "fortytwo_app_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default 1).
limitNoResults per page (1-50). Default 10.
queryYesSearch term, e.g. "racing games", "meditation".
_apiKeyYes42matters API access token (get one at https://42matters.com/pricing).
platformNoApp store to query: "android" (Google Play) or "ios" (Apple App Store). Defaults to "android".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds only that results are paginated, which is useful but thin; no rate limits, result caps, or auth nuance beyond the schema's _apiKey note.

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?

Two compact sentences with the purpose front-loaded before the example. The inline example is slightly redundant with the schema's own examples array, which keeps it from a perfect score.

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 low-complexity, read-only search tool with full schema coverage and annotations, the definition is largely complete. Without an output schema it could say more about return shape, but the pagination hint partially covers that.

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 description coverage is 100%, so all five parameters are already documented, including defaults and the platform enum. The description's example adds no parameter meaning beyond what the schema provides, so baseline 3 applies.

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 (search) and resource (app store) with the keyword input and pagination outcome. It distinguishes itself from lookup/charts-style siblings by nature of being keyword-driven, though it doesn't explicitly name any sibling.

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 keyword-search framing implies when to use it, and the example clarifies the invocation, but there is no explicit when/when-not guidance and no routing against siblings like fortytwo_app_lookup or fortytwo_top_charts.

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

All 42matters 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