Skip to main content
Glama
Sign In

OneStore

by so.onestore
OverviewDiscussionsAdmin

Check app links

check_app_links
Read-onlyIdempotent

Verify Android App Links and iOS Universal Links for up to 5 hosts: fetches assetlinks.json and apple-app-site-association without following redirects, then reads what Google’s Digital Asset Links API and Apple’s CDN hold. Defaults to the hosts of the app’s website and listing URLs.

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": {
      "appId": "<appId>"
    },
    "name": "check_app_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes
hostsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely new behavioral facts: redirects are NOT followed, results come from both live host fetches and Google's Digital Asset Links API / Apple's CDN, and there is a hard 5-host cap.

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?

A single dense sentence front-loaded with the verb and resource, with no filler. It is information-rich rather than bloated, though the clause chain about the two upstream APIs makes it slightly heavy to parse.

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?

With no output schema, the description is the only place result shape can be conveyed, and it never says what a verification result looks like (per-host pass/fail, which platform failed, partial failures when a host is unreachable). The inputs and mechanism are complete; the outcome contract is not.

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 0%, so the description must carry parameter meaning. It does well for 'hosts' (max 5, defaults to the app's website and listing URLs) but says nothing about 'appId' — format, whether it is a package name, bundle ID, or a platform-specific identifier — leaving a real ambiguity.

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 verb (verify) and specific resources (Android App Links, iOS Universal Links) and even names the concrete artifacts fetched (assetlinks.json, apple-app-site-association). No sibling tool does anything similar, so an agent can route to it unambiguously.

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?

Explains the operating context (validation of deep-link association files) and the default host derivation, which tells the agent it can call with only appId. It stops short of explicit when-not guidance or naming alternatives, but no sibling overlaps this capability.

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

All OneStore toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources